Igor Pechtchanski wrote: > I'm getting intermittent hangs in latest build of setup. Gdb > backtrace shows: > (gdb) thread 1 > [Switching to thread 1 (thread 3084.0xb18)]#0 0x77e11b80 in > USER32!DestroyWindow () from /cygdrive/c/WINNT/system32/USER32.DLL > (gdb) where #0 0x77e11b80 in USER32!DestroyWindow () > from /cygdrive/c/WINNT/system32/USER32.DLL > #1 0x77e11e09 in USER32!GetMessageW () > from /cygdrive/c/WINNT/system32/USER32.DLL > #2 0x7171f4f6 in FlatSB_EnableScrollBar () > #3 0x7171f2dd in FlatSB_EnableScrollBar () > #4 0x71721ba8 in DrawStatusTextW () > #5 0x0043683c in PropSheet::Create(Window const*, unsigned long) ( > this=0x22f9b0, Parent=0x0, Style=315555840) > at /usr/src/setup-cvs/setup/propsheet.cc:193 > #6 0x004250de in WinMain (h=0x400000, hPrevInstance=0x0, > command_line=0x2332c6 "", cmd_show=1) > at /usr/src/setup-cvs/setup/main.cc:370 > #7 0x00456a43 in main () at > /usr/include/c++/3.2/bits/char_traits.h:147 (gdb) > This is apparently somewhere inside the PropertySheet() Windows > function. > > Is this a known issue? What would be the best way to debug this?
I haven't run into this. That backtrace looks a little odd - anyone know whether gdb could be incorrectly decoding the addresses in Windows DLLs? Exactly what is happening when the hang occurs? Max.
