This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] breakpoints and function prologues...
- From: Joel Brobecker <brobecker at gnat dot com>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: Daniel Jacobowitz <drow at mvista dot com>,Andrew Cagney <ac131313 at ges dot redhat dot com>,gdb-patches at sources dot redhat dot com
- Date: Thu, 22 Aug 2002 15:56:44 -0700
- Subject: Re: [RFC] breakpoints and function prologues...
- References: <6AF1E816-A97C-11D6-B045-00039379E320@> <3D5B42B9.6070201@ges.redhat.com> <20020815135338.GA22990@nevyn.them.org> <3D656658.9D01C76D@redhat.com>
> The question is, is there a strong reason to change a behavior
> that has been consistent for a very long time (even if undocumented).
> Even if the ability to debug the prologue is un-important for most
> users, it is important to some, and those users (GCC developers,
> for instance) may be quite accustomed to the current behavior.
> I am, for instance...
I would not say a "strong" reason, but as you say, the user base has
shifted, and supposing that ACT's customer base is representative of the
user base, a good part of the users are surprised by the current
behavior.
Incidentally, it would make the new behavior more in line with the
behavior seen when breaking by function name. If later we decide to
change the "break funcname" to stop skipping prologues because GDB now
has all the machinery that makes the skipping unnecessary, I would
likewise argue that we should change back the behavior of "break
linenum" as well.
--
Joel