This is the mail archive of the archer@sourceware.org mailing list for the Archer 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: Stack trace from core file without executable

From: Daniel Jacobowitz <drow at false dot org>
To: Paul Pluzhnikov <ppluzhnikov at google dot com>
Cc: Ray Ruvinskiy <rruvinsk at sybase dot com>, archer at sourceware dot org
Date: Mon, 20 Oct 2008 14:02:24 -0400
Subject: Re: Stack trace from core file without executable
References: <84F62FF9-ED8B-40D3-9C2C-384E59DE955F@sybase.com> <8ac60eac0810181519r4fe246d0hfa83fdb13d8e1a1d@mail.gmail.com> <DD2B6F11-B3EB-4ADF-A29F-BEAE851D2D10@sybase.com> <8ac60eac0810201040s144c92a8s8b64af9d170331d7@mail.gmail.com>

On Mon, Oct 20, 2008 at 10:40:46AM -0700, Paul Pluzhnikov wrote:
> > [New process 23913]
> > #0  0xb7f08410 in __kernel_vsyscall ()
> > #0  0xb7f08410 in __kernel_vsyscall ()
> > #1  0xb7dd4085 in ?? ()
> 
> Frame #1 above is correct; I wonder what causes the rest of it to
> go wrong :-( ...

IIRC there's a patch in someone's (SuSE's?) GDB packages that improves
success for %ebp-based backtracing.  Some bit of GDB decides that
missing symbols are frameless functions, which is a debatable choice.
Ref: debian bug 498030, http://bugs.debian.org/498030 .

-- 
Daniel Jacobowitz
CodeSourcery

References:
- Stack trace from core file without executable
  - From: Ray Ruvinskiy
- Re: Stack trace from core file without executable
  - From: Paul Pluzhnikov
- Re: Stack trace from core file without executable
  - From: Ray Ruvinskiy
- Re: Stack trace from core file without executable
  - From: Paul Pluzhnikov

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