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: Avoid timeouts in call-sc.exp


Paul Gilliam <pgilliam@us.ibm.com> wrote:
> Here is the $64000 question: why did GDB recognize we were in the
> outermost frame for the 32-bit case and not for the 64-bit case?

Two things at a time.

The problem in call-sc.exp is that it assumes that the inferior
program is at a well-defined location after 'return'.  When that's
not true, it derails.  I want to get that fixed.

The problem in gdb is that 'return' is the I/O error on fpscr.

It's yet another issue about recognizing the outermost frame
on different ports, and I'm not going to care about that now.


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