| www.delorie.com/archives/browse.cgi | search |
Hi! Friday, 21 September, 2001 Jason Tishler jason AT tishler DOT net wrote: JT> I finally found out why JIT debugging was not working for me. It appears JT> that I needed to "chmod +x c:/debug.bat". After making c:/debug.bat JT> executable, I was able to trigger JIT debugging with your test program: hmm. it looks almost obvious for windows, where file are created with full access for everyone, but it certainly not so for unix. i'll try to make this point a bit clearer. JT> Unfortunately, JIT debugging is not triggering with the following threaded JT> Python problem: JT> test_socket JT> 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 JT> 0 [main] python 2016 sync_with_child: child 2100(0x288) died before initialization with status code 0x1 JT> 3716 [main] python 2016 sync_with_child: *** child state child loading dlls test test_socket crashed -- exceptions.OSError: [Errno 11] Resource temporarily unavailable JT> Should JIT debugging trigger for the above condition too? no. JIT debugging facility is being initialized at program startup. early enough, but not too early. if something goes wrong before that, JIT debugger won't be called. see file 'how-to-debug-cygwin.txt' in winsup/cygwin/ directory of sources. it contains some techniques that may help in this case (as well as in the others). Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |