unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Steven Parkes <smparkes@smparkes.net>
Cc: 11583@debbugs.gnu.org
Subject: bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames
Date: Wed, 30 May 2012 18:11:57 +0300	[thread overview]
Message-ID: <83sjeh1z5u.fsf@gnu.org> (raw)
In-Reply-To: <97C29B43-62E2-48FD-BEC2-EA851BC5E158@smparkes.net>

> From: Steven Parkes <smparkes@smparkes.net>
> Date: Tue, 29 May 2012 20:07:28 -0700
> Cc: "11583@debbugs.gnu.org" <11583@debbugs.gnu.org>
> 
> 
> On May 29, 2012, at 7:52 PM, Eli Zaretskii wrote:
> 
> > Can you tell what is error_symbol and data in frame #31 and what
> > symbol is being passed to Fsymbol_value in frame #34?
> 
> Can you give me hints on how to answer this? Something I can do in gdb?

Yes, in GDB.  Like this:

 (gdb) fr 31
 (gdb) p error_symbol
 (gdb) xtype

According to what "xtype" says, use the appropriate x* command to
display the Lisp object.  For example, if "xtype" says it's a symbol,
use "xsymbol", for strings use "xstring", etc.  (You will have to make
sure src/.gdbinit is sourced before you can use the x* commands.)

> I could try building w/o optimizations and see if it still fails. If it does, presumably I can get more info from gdb more easily.

That would be even better.

> Got it. Just looked up how to do this. I overlooked where it was defined on the first go around. Sorry 'bout that.

If you start GDB from the src directory, this works automagically,
because .gdbinit is read and xbacktrace is invoked after each "bt".

Thanks.





  reply	other threads:[~2012-05-30 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 18:48 bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames Steven Parkes
2012-05-29 20:55 ` bug#11584: " Steven Parkes
     [not found]   ` <handler.11584.B.133834111624627.ack@debbugs.gnu.org>
2012-05-30  1:27     ` bug#11584: Acknowledgement (24.0.97; 24 pretest Emacs.app crashes closing frames) Steven Parkes
2012-05-30  2:52 ` bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames Eli Zaretskii
2012-05-30  3:07   ` Steven Parkes
2012-05-30 15:11     ` Eli Zaretskii [this message]
2012-05-30 15:45       ` Steven Parkes
2012-06-03  2:05   ` Steven Parkes
2012-06-03 14:54     ` Eli Zaretskii
2012-06-04 20:30       ` Steven Parkes
2012-06-04 21:09         ` Jan Djärv
2012-06-04 21:11           ` Steven Parkes
2012-06-11 16:57             ` Jan Djärv
2012-06-11 17:31               ` Andreas Schwab
2012-06-12  2:52               ` Steven Parkes
2012-07-14  9:10         ` bug#7879: 24.0.50; Wish: Make c-defun-name recognize objc-methods Jan Djärv
     [not found] ` <handler.11583.B.133834111324619.ack@debbugs.gnu.org>
2012-07-02 20:43   ` bug#11583: (24.0.97; 24 pretest Emacs.app crashes closing frames) Steven Parkes

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=83sjeh1z5u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11583@debbugs.gnu.org \
    --cc=smparkes@smparkes.net \
    /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).