This is the mail archive of the gdb-patches@sourceware.org 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: Fix for PR 1971 .


On 1/3/06, Ramana Radhakrishnan <ramana.radhakrishnan@codito.com> wrote:
> Attached is a fix for PR 1971. This inserts a breakpoint at the return
> address for a function that does not have a previous frame which is what
> you have in the case of main. This would however not stop after the
> return from main because the semantics of the next command would not
> stop the execution in any place where there is no debug information.
>
> Tested on native x86 with today's head as well as 6.4 branch with no
> extra regressions .

Is this the behavior we actually want?  Where the user hasn't "set
backtrace past-main on", isn't it the correct behavior for GDB to
allow the program to exit when doing a 'next' out of main?  (I assume
that, if one does a 'set backtrace past-main on', then 'next' works as
you suggest it should.)


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