This is the mail archive of the gdb-patches@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: The gdb x86 function prologue parser

> Date: Sun, 12 Jun 2005 09:48:07 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: gdb-patches@sources.redhat.com
> 
> 1. Finding out the gory details about the stack frame being executed.
> 
> 2. Determining the first bit of code after the prologue, i.e. the
>    first bit of real code.
> 
> For (2) following jumps is usually a very bad thing to do.
> 
> That said, I'm not sure this dual usage of the prologue scanner really
> makes sense these days.  There is a certain lack of consistency in gdb
> how we handle this anyway.  Maybe the best thing to do is to not use
> the prologue scanner for 2 at all.

In what situations would GDB need to use (2), and what are the
alternative(s)?
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]