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


Eli Zaretskii wrote:
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, jason-swarelist@molenda.com,
       gdb-patches@sources.redhat.com
From: Klee Dienes <klee@mit.edu>
Date: Sun, 12 Jun 2005 07:59:01 -0400

(2) gets used by GDB when it wants to know where to set a breakpoint (the idea being that when you say "break foo", it wants to insert the breakpoint in foo() after the prologue has been fully executed).

It also gets used where GDB wants to know if it is inside a function prologue for some reason (for example, so "next" knows if it has stepped into a new function, or simply jumped interprocedurally).


Thanks.

(I'm collecting info for gdbint.texinfo, that's why I asked.)

Also so "step into" can step past the prologue and not stop until it has reached user code. Same basic purpose as 2), but different context.



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