From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: romain@orebokech.com, 7952@debbugs.gnu.org
Subject: bug#7952: 24.0.50; crash in find_interval
Date: Sat, 19 Mar 2011 14:51:25 +0200 [thread overview]
Message-ID: <83zkor9stu.fsf@gnu.org> (raw)
In-Reply-To: <m2tyezxq6f.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Romain Francoise <romain@orebokech.com>, 7952@debbugs.gnu.org
> Date: Sat, 19 Mar 2011 13:14:48 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > There's nothing in this code that modifies `tree' in any way. (I even
> > disassembled the code to make sure.) So how come a non-NULL value
> > becomes NULL here?
>
> It isn't, otherwise you would get a crash.
Unless it happens after the place where `tree' is dereferenced.
> > Since this value is passed in a register by the caller and kept in a
> > register from the very beginning of the function, not even some
> > missing GCPRO somewhere could explain this. What am I missing?
>
> Probably your toolchain is too old to be able to produce complete unwind
> information.
I doubt that, since it's GDB 7.2. Maybe it's a GCC problem.
> Try setting a breakpoint at the abort line to get a better picture.
It's a core file. Romain, could you try that, perhaps?
In any case, we could look at TOTAL_LENGTH of the pointer in the frame
where it has a non-NULL value.
next prev parent reply other threads:[~2011-03-19 12:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1296565545.10637.bug-gnu-emacs@gnu.org>
2011-03-09 12:25 ` bug#7952: 24.0.50; crash in find_interval Romain Francoise
2011-03-09 13:46 ` Eli Zaretskii
2011-03-09 15:16 ` Romain Francoise
2011-03-18 19:19 ` Romain Francoise
2011-03-18 19:37 ` Eli Zaretskii
2011-03-18 20:45 ` Romain Francoise
2011-03-19 10:37 ` Eli Zaretskii
2011-03-19 12:14 ` Andreas Schwab
2011-03-19 12:51 ` Eli Zaretskii [this message]
2011-03-19 13:18 ` Andreas Schwab
2011-03-19 13:56 ` Romain Francoise
2011-04-13 21:06 ` Chong Yidong
2011-04-14 4:36 ` Eli Zaretskii
2011-04-14 13:18 ` Romain Francoise
2011-04-26 8:39 ` Romain Francoise
2011-04-26 17:52 ` Eli Zaretskii
2011-04-29 18:17 ` Eli Zaretskii
2011-04-29 20:42 ` Romain Francoise
2011-04-30 8:58 ` Eli Zaretskii
2011-04-30 13:16 ` Stefan Monnier
2011-04-30 13:24 ` Eli Zaretskii
2011-05-02 14:51 ` Stefan Monnier
2011-05-08 5:18 ` Chong Yidong
2011-05-08 15:28 ` Eli Zaretskii
2011-05-08 20:27 ` Chong Yidong
2011-05-09 6:24 ` Eli Zaretskii
2011-05-09 14:06 ` Stefan Monnier
2011-05-09 14:46 ` Eli Zaretskii
2011-05-09 15:32 ` Stefan Monnier
2011-05-09 15:42 ` Eli Zaretskii
2011-05-09 17:09 ` Stefan Monnier
2011-05-09 19:46 ` Chong Yidong
2011-05-09 20:31 ` Eli Zaretskii
2011-02-01 12:41 Romain Francoise
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zkor9stu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7952@debbugs.gnu.org \
--cc=romain@orebokech.com \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.