Emacs C debug help function?

Emacs C debug help function?

[Shenli Zhu]

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

Hi Emacs hackers.

I have tried to understand function (debug) on elisp level, and find some
details on C level(e.g. debugger-step-after-exit).
So, I attach emacs process to gdb.

Backtrace is like:
...
#14 0x0818f78b in Ffuncall (nargs=1, args=0xbfa63a00) at eval.c:3021
#15 0x081c8d21 in Fbyte_code (bytestr=154800713, vector=166927821,
maxdepth=16)
    at bytecode.c:680
#16 0x081911b2 in Feval (form=165809550) at eval.c:2352
...

Is there any help function to display form, etc? And is there any
instruction files on hacking C files?

Thanks,
Davy

[-- Attachment #2: Type: text/html, Size: 612 bytes --]

Emacs C debug help function?

[Stephen J. Turnbull]

Shenli Zhu writes:

 > Is there any help function to display form, etc?

Yes.  Type "help user" to gdb for an annotated list.  If you don't
understand how to use them from that list, or need help interpreting
results, please ask specifically.

 > And is there any instruction files on hacking C files?

For advice on writing code, as far as I know there is a little bit in
the Emacs Lisp Reference, and for the general structure of C support
for Lisp, online there's

    http://www.xemacs.org/Documentation/21.5/html/internals.html

Warning: Emacs and XEmacs redisplays are completely different, as are
text properties and extents.  The Lisp language implementation is
pretty similar, as are the buffer and string structures.  (You need to
be a little careful with text as XEmacs still uses Mule code
internally, but it has the same formal properties, eg, finding
character boundaries in O(1), etc, and many of the same higher-level
APIs for actually handling encoding as used in Emacs.)

For the style you should use in writing code, there is the GNU coding
standard, which I believe is distributed somewhere with Emacs.  If
not, you can install XEmacs and throw away everything except the
"standards.info" file. :-)  (Sorry, we don't provide an online
version.  Probably somewhere on the GNU site?)

Re: Emacs C debug help function?

[Glenn Morris]

Shenli Zhu wrote:

> Backtrace is like:
> ...
> #14 0x0818f78b in Ffuncall (nargs=1, args=0xbfa63a00) at eval.c:3021
> #15 0x081c8d21 in Fbyte_code (bytestr=154800713, vector=166927821,
> maxdepth=16)
>     at bytecode.c:680
> #16 0x081911b2 in Feval (form=165809550) at eval.c:2352
> ...
>
> Is there any help function to display form, etc?

Try reading etc/DEBUG.

Re: Emacs C debug help function?

[Shenli Zhu]

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

On Fri, Sep 10, 2010 at 12:02 PM, Glenn Morris <rgm@gnu.org> wrote:

> Shenli Zhu wrote:
>
> > Backtrace is like:
> > ...
> > #14 0x0818f78b in Ffuncall (nargs=1, args=0xbfa63a00) at eval.c:3021
> > #15 0x081c8d21 in Fbyte_code (bytestr=154800713, vector=166927821,
> > maxdepth=16)
> >     at bytecode.c:680
> > #16 0x081911b2 in Feval (form=165809550) at eval.c:2352
> > ...
> >
> > Is there any help function to display form, etc?
>
> Try reading etc/DEBUG.
>

Hi Glenn, it's informative, thank you.

[-- Attachment #2: Type: text/html, Size: 856 bytes --]

Re: Emacs C debug help function?

[Shenli Zhu]

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

On Fri, Sep 10, 2010 at 11:37 AM, Stephen J. Turnbull <stephen@xemacs.org>wrote:

> Shenli Zhu writes:
>
>  > Is there any help function to display form, etc?
>
> Yes.  Type "help user" to gdb for an annotated list.  If you don't
> understand how to use them from that list, or need help interpreting
> results, please ask specifically.
>
>  > And is there any instruction files on hacking C files?
>
> For advice on writing code, as far as I know there is a little bit in
> the Emacs Lisp Reference, and for the general structure of C support
> for Lisp, online there's
>
>    http://www.xemacs.org/Documentation/21.5/html/internals.html
>
> Warning: Emacs and XEmacs redisplays are completely different, as are
> text properties and extents.  The Lisp language implementation is
> pretty similar, as are the buffer and string structures.  (You need to
> be a little careful with text as XEmacs still uses Mule code
> internally, but it has the same formal properties, eg, finding
> character boundaries in O(1), etc, and many of the same higher-level
> APIs for actually handling encoding as used in Emacs.)
>
> For the style you should use in writing code, there is the GNU coding
> standard, which I believe is distributed somewhere with Emacs.  If
> not, you can install XEmacs and throw away everything except the
> "standards.info" file. :-)  (Sorry, we don't provide an online
> version.  Probably somewhere on the GNU site?)
>

Hi Stephen, it's what I need, thank you.

[-- Attachment #2: Type: text/html, Size: 2063 bytes --]