From: Dan Nicolaescu <dann@ics.uci.edu>
To: raman@users.sourceforge.net
Cc: rgm@gnu.org, rms@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: 23.0.50; Emacs 23.0.50: Segfaults in alloc.c (batch process)
Date: Tue, 25 Sep 2007 20:28:31 -0700 [thread overview]
Message-ID: <200709260328.l8Q3SZhu012787@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <18169.53072.224179.467917@gargle.gargle.HOWL> (T. V. Raman's message of "Tue\, 25 Sep 2007 20\:17\:36 -0700")
"T. V. Raman" <raman@users.sf.net> writes:
> Here is the output of the two commands you requested.
Please send the output of xbacktrace, not backtrace.
> What would help me chase this down further would be some gdb
> bindings that let me examine the various lisp_objects on the
> stack.
Look in emacs/src/.gdbinit there are all kinds of gdb commands to look
at various lisp data structures. xbacktrace is defined there too.
next prev parent reply other threads:[~2007-09-26 3:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 3:12 23.0.50; Emacs 23.0.50: Segfaults in alloc.c (batch process) raman
2007-09-10 1:13 ` Richard Stallman
2007-09-17 0:20 ` Richard Stallman
2007-09-23 21:55 ` Richard Stallman
2007-09-24 0:15 ` T. V. Raman
2007-09-24 0:22 ` Glenn Morris
2007-09-24 2:15 ` T. V. Raman
2007-09-24 2:40 ` Glenn Morris
2007-09-24 12:34 ` T. V. Raman
2007-09-24 19:43 ` Glenn Morris
2007-09-24 19:48 ` David Kastrup
2007-09-25 17:57 ` Richard Stallman
2007-09-25 22:23 ` Leo
2007-09-26 19:00 ` selective citation (was: 23.0.50; Emacs 23.0.50: Segfaults in alloc.c (batch process)) Reiner Steib
2007-09-26 21:09 ` selective citation Leo
2007-09-25 3:23 ` 23.0.50; Emacs 23.0.50: Segfaults in alloc.c (batch process) T. V. Raman
2007-09-25 17:37 ` Glenn Morris
2007-09-26 3:17 ` T. V. Raman
2007-09-26 3:28 ` Dan Nicolaescu [this message]
2007-09-25 14:35 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709260328.l8Q3SZhu012787@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-pretest-bug@gnu.org \
--cc=raman@users.sourceforge.net \
--cc=rgm@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).