From: Daniel Jacobowitz <drow@false.org>
To: Dave Korn <dk@artimi.com>
Cc: 'Mark Kettenis' <kettenis@chello.nl>,
eliz@gnu.org, cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: [6.2] PROBLEMS file
Date: Thu, 22 Jul 2004 15:17:00 -0000 [thread overview]
Message-ID: <20040722130301.GA14326@nevyn.them.org> (raw)
In-Reply-To: <NUTMEGVnfqTWW06831a000009f1@NUTMEG.CAM.ARTIMI.COM>
On Thu, Jul 22, 2004 at 01:13:19PM +0100, Dave Korn wrote:
> > -----Original Message-----
> > From: gdb-owner On Behalf Of Mark Kettenis
> > Sent: 21 July 2004 22:00
>
> > shouldn't terminate the backtrace. And %eip == 0 can happen in the
> > case of a null-pointer function call.
>
> Does it? I thought the stored eip on the stack points to the return
> address of the caller, which is the byte after the call instruction, so eip
> = 0 would only occur in a stack frame if there was a call instruction at
> 0xfffffffb that had just been executed?
Consider a SIGSEGV handler invoked in response to a NULL pointer call.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-22 13:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 3:51 Andrew Cagney
2004-07-19 21:01 ` Eli Zaretskii
2004-07-21 21:12 ` Mark Kettenis
2004-07-21 22:05 ` H. J. Lu
2004-07-22 20:58 ` Mark Kettenis
2004-07-22 21:33 ` Joel Brobecker
2004-07-22 21:38 ` H. J. Lu
2004-07-21 22:17 ` Andrew Cagney
2004-07-22 7:13 ` Eli Zaretskii
2004-07-22 13:04 ` Dave Korn
2004-07-22 15:17 ` Daniel Jacobowitz [this message]
2004-07-22 12:14 Michael Elizabeth Chastain
2004-07-22 18:28 ` Joel Brobecker
2004-07-22 19:26 ` Eli Zaretskii
2004-07-22 20:51 ` Mark Kettenis
2004-07-23 9:24 ` Eli Zaretskii
2004-07-23 11:22 ` Mark Kettenis
2004-07-23 12:03 ` Eli Zaretskii
2004-07-23 12:13 ` Eli Zaretskii
2004-07-23 12:16 ` Dave Korn
2004-07-23 13:36 ` Mark Kettenis
2004-07-23 16:17 ` Eli Zaretskii
2004-07-23 5:44 Michael Elizabeth Chastain
2004-07-23 20:44 ` Andrew Cagney
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=20040722130301.GA14326@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=dk@artimi.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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.
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).