This is the mail archive of the cygwin mailing list for the Cygwin 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: Question on gdb and ?? And also Frame did not save PC message

Brian Keener wrote:

> As to the second part of my question - is there a way to determine what
> sources/debug info I still need to get around the ?? Or is that just a
> matter of tracing from the sources I can see to find what it is bing
> called next?

Most of those frames with ?? are totally bogus -- there is not actually
a frame at 0x00000028 or 0x00000001 etc., it's just that gdb got
confused trying to unwind the stack and did its best.  One problem is
that Cygwin uses these sigfe/sigfe wrappers around most syscalls,
another is that gdb doesn't have debug info for system DLLs and if they
use FPO there's no way to unwind through them.

> Also when using the new gdb is the message about
> "Frame did not save PC message" expected or is that an indication of some
> limit exceeded or something else.

It's just another an indication that gdb is having trouble unwinding, as
with system DLLs with FPO enabled.


Unsubscribe info:
Problem reports:

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