Re: stack trace and breaking before crash

On Tue, Mar 11, 2008 at 10:45:08AM -0700, Brian Dessent
wrote:
> I don't think you're doing anything wrong.  It looks
like the JIT
> debugger code in Cygwin and/or dumper might need some
bugfixes.  The
> reason that continuing works is that it simply
retriggers the fault
> again at the same location where it faulted the first
time.  Apparently
> at the point where gdb and/or dumper attaches to the
process, the
> location of the fault is already lost and execution is
somewhere inside
> the ntdll bowels in the exception handling code.

Try info threads?  IIRC the debug connection is the
"current" thread,
and the app is otherwise in a suspended thread.

-- 
Daniel Jacobowitz
CodeSourcery

Daniel Jacobowitz wrote:

> Try info threads?  IIRC the debug connection is the
"current" thread,
> and the app is otherwise in a suspended thread.

Yes, that's the reply I had typed out at first but then I
tried it to
make sure and all three threads are off in ntdll somewhere.

Brian