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: [RFC] Prints the frame id when target stops


Frederic RISS <frederic.riss@st.com> writes:
>> I suspect you can only do this in stepi, really - step/next can end up
>> in strange places...
>
> ... and end up in a frame with the same frame id? Seems unlikely, but
> then GDB isn't the place where you'd want to trade accuracy for a very
> small speedup.

Yeah --- I'd be very concerned about GDB performance optimizations
that would cause GDB to not notice, say, corruptions of the stack by
buffer overruns.

If it's common for memory reads to be so expensive, you should buy a
better JTAG unit^W^W^W^W^W^W^W I'd rather we work on minimizing memory
accesses by unwinders than make assumptions which may not hold in
buggy programs.

Could you enable 'debug remote' while it's doing the unwinding, and
figure out what it's actually fetching?


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