This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [6.2] PROBLEMS file

From: Daniel Jacobowitz <drow at false dot org>
To: Dave Korn <dk at artimi dot com>
Cc: 'Mark Kettenis' <kettenis at chello dot nl>, eliz at gnu dot org, cagney at gnu dot org,gdb at sources dot redhat dot com
Date: Thu, 22 Jul 2004 09:03:02 -0400
Subject: Re: [6.2] PROBLEMS file
References: <200407212059.i6LKxgQ9019045@copland.kettenis.dyndns.org> <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

References:
- Re: [6.2] PROBLEMS file
  - From: Mark Kettenis
- RE: [6.2] PROBLEMS file
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]