Mail Archives: cygwin-developers/2001/09/21/09:13:40
Chris,
On Tue, Sep 11, 2001 at 09:53:41PM -0400, Christopher Faylor wrote:
> On Tue, Sep 11, 2001 at 09:08:54PM -0400, Jason Tishler wrote:
> >On Tue, Sep 11, 2001 at 08:40:19PM -0400, Jason Tishler wrote:
> >> On Wed, Sep 12, 2001 at 09:19:19AM +1000, Robert Collins wrote:
> >> > If it was after the bugfix commit, I'd like to see if we can track this
> >> > asap...
> >>
> >> I can reproduce it frequently but not every time. I will debug it first
> >> thing tomorrow morning. FYI, it seems to occur right near the end of
> >> the test and the test still passes.
> >
> >I'm also having cockpit error trying to use error_start. I have tried
> >the following:
> >
> > binmode notty ntsec error_start:c:/debug.bat
> >
> >and
> >
> > binmode notty ntsec error_start=c:/debug.bat
> > *
> >With debug.bat as follows:
> >
> > $ cat c:/debug.bat
> > C:/Cygwin/bin/gdb.exe -nw %1 %2 %3 %4 %5
> >
> >With the above, when broadcast GPFs, gdb is not started. Any idea what
> >I'm doing wrong?
>
> Both examples look right.
>
> This is one of those situations where I would just debug cygwin to
> see why it isn't working as advertised.
I finally found out why JIT debugging was not working for me. It appears
that I needed to "chmod +x c:/debug.bat". After making c:/debug.bat
executable, I was able to trigger JIT debugging with your test program:
> Write a simple test program (tst.c) that dereferences zero:
>
> int
> main(int argc, char **argv)
> {
> int *i = 0;
> *i = 1;
> }
Unfortunately, JIT debugging is not triggering with the following threaded
Python problem:
test_socket
C:\home\jt\src\python-2.1.1\python.exe: *** unable to remap C:\home\jt\src\python-2.1.1\build\lib.cygwin-1.3.4-i686-2.1\rotor.dll to same address as parent -- 0x69180000
0 [main] python 2016 sync_with_child: child 2100(0x288) died before initialization with status code 0x1
3716 [main] python 2016 sync_with_child: *** child state child loading dlls test test_socket crashed -- exceptions.OSError: [Errno 11] Resource temporarily unavailable
Should JIT debugging trigger for the above condition too?
Thanks,
Jason
- Raw text -