Re: [boost] [1.39.0] Beta candidate

Subject: Re: [boost] [1.39.0] Beta candidate
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2009-04-27 12:48:53

Eric Niebler wrote:

> Vladimir Prus wrote:
>> Try:
>> 
>>         thread apply all backtrace
>> 
>> to get backtrace in all threads. I'm not overly optimistic :-(
> 
> 
> Boost.Build V2 (Milestone 12)
> Boost.Jam 03.1.17
> 
> (no debugging symbols found)
> [New thread 636680.0x9b020]
> [New thread 636680.0x9b694]
> [New thread 636680.0x9b670]
> 
> Program received signal SIGINT, Interrupt.
> [Switching to thread 636680.0x9b670]
> 0x762f6e39 in PulseEvent (Quit
> (gdb) thread apply all backtrace
> 
> Thread 6 (thread 636680.0x9b670):
> #0  0x762f6e39 in PulseEvent () from
> /cygdrive/c/Windows/system32/kernel32.dll
> #1  0x61004416 in _cygtls::call2 () from /usr/bin/cygwin1.dll
> #2  0x00000000 in ?? ()
> 
> Thread 5 (thread 636680.0x9b694):
> #0  0x76fa9a94 in ntdll!LdrAccessResource () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #1  0x76fa9254 in ntdll!ZwWaitForSingleObject () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #2  0x762dc244 in WaitForSingleObjectEx () from
> /cygdrive/c/Windows/system32/kernel32.dll
> #3  0x000001e0 in ?? ()
> #4  0x00000000 in ?? ()
> 
> Thread 4 (thread 636680.0x9b020):
> #0  0x76fa9a94 in ntdll!LdrAccessResource () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #1  0x76fa9254 in ntdll!ZwWaitForSingleObject () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #2  0x762dc244 in WaitForSingleObjectEx () from
> /cygdrive/c/Windows/system32/kernel32.dll
> #3  0x000001fc in ?? ()
> #4  0x00000000 in ?? ()
> 
> Thread 3 (thread 636680.0x9b7d4):
> #0  0x76fa9a94 in ntdll!LdrAccessResource () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #1  0x76fa8c74 in ntdll!ZwReadFile () from
> /cygdrive/c/Windows/system32/ntdll.dll
> #2  0x762d046b in ReadFile () from /cygdrive/c/Windows/system32/kernel32.dll
> #3  0x00000110 in ?? ()
> #4  0x00000000 in ?? ()
> 
> Thread 1 (thread 636680.0x9b5c0):
> #0  0x00411232 in ?? ()
> #1  0x00fb22c0 in ?? ()
> #2  0x00229354 in ?? ()
> #3  0x00229368 in ?? ()
> #4  0x00407538 in ?? ()
> #5  0x01971f27 in ?? ()
> #6  0x010e16bc in ?? ()
> #7  0x002295cc in ?? ()
> #8  0x01088553 in ?? ()
> #9  0x01088553 in ?? ()
> #10 0x01088551 in ?? ()
> #11 0x00229a08 in ?? ()
> #12 0x00403771 in ?? ()
> #13 0x002295c0 in ?? ()
> #14 0x01088551 in ?? ()
> #15 0x01088551 in ?? ()
> #16 0x00229de8 in ?? ()
> #17 0x00000000 in ?? ()
> #0  0x762f6e39 in PulseEvent () from
> /cygdrive/c/Windows/system32/kernel32.dll
> 
> 
> Looks like bjam.exe is missing debug symbols. Is there a way to build a
> debug bjam.exe, perhaps using jam/src/build.sh?

Now that you mention it, adding --debug option to jam/src/build.sh might help, indeed.
I think that it will be built to a separate dir, bin.something.debug, not bin.something
as usual.

- Volodya