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 05:52:26 +0300	[thread overview]
Message-ID: <83txyy1itx.fsf@gnu.org> (raw)
In-Reply-To: <EB111772-0B57-45BD-BEE8-848C70980A06@smparkes.net>

> From: Steven Parkes <smparkes@smparkes.net>
> Date: Tue, 29 May 2012 11:48:34 -0700
> 
> #31 0x000000010012a6a3 in Fsignal (error_symbol=4569131382, data=140734799799648) at eval.c:1752
> 	combined_data = 4499731520
> 	conditions = 4499731520
> 	bp = (struct backtrace *) 0x7fff5fbfe418
> 	string = 4499731520
> #32 0x000000010012e419 in xsignal (error_symbol=4328590586, data=4569131078) at eval.c:1786
> No locals.
> #33 0x000000010012d7bf in xsignal1 (error_symbol=<value temporarily unavailable, due to optimizations>, arg=<value temporarily unavailable, due to optimizations>) at eval.c:1801
> No locals.
> #34 0x00000001001172c9 in Fsymbol_value (symbol=<value temporarily unavailable, due to optimizations>) at data.c:1059
> 	val = 4499731520
> #35 0x000000010012cc18 in eval_sub (form=4641613202) at eval.c:2232
> 	lex_binding = 4499731520
> 	original_args = 4329147226
> 	original_fun = 4328534074
> 	backtrace = {next = 0x10037fee5, function = 0x7fff5fbfe788, args = 0x92978a07a3b36f34, nargs = 4298636920, debug_on_exit = 0}
> #36 0x000000010012abed in Feval (form=4641613202, lexical=4569131078) at eval.c:2204
> 	count = 9

Can you tell what is error_symbol and data in frame #31 and what
symbol is being passed to Fsymbol_value in frame #34?

Also, a Lisp backtrace (xbacktrace) would be nice.





  parent reply	other threads:[~2012-05-30  2:52 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 ` Eli Zaretskii [this message]
2012-05-30  3:07   ` bug#11583: 24.0.97; 24 pretest Emacs.app crashes closing frames Steven Parkes
2012-05-30 15:11     ` Eli Zaretskii
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=83txyy1itx.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).