No help?

[Uwe Bonnes]

Bjarne Wichmann Petersen <mekanix at nospam.dk> wrote:
: In article <97d5hk$3q8$1 at sun27.hrz.tu-darmstadt.de>, "Uwe Bonnes"
: <bon at elektron.ikp.physik.tu-darmstadt.de> wrote:

:> As has proposed many times before, run with --debugmsg +relay and
:> look where you suspect the hang.  Is there an API call hanging
:> forever or is there a loop?

: No loop, these are the last debug-messages:

: trace:relay:WINPROC_CallWndProc (wndproc=0x286a9488,hwnd=00000a14,msg=WM_CTLCOLORBTN,wp=00000048,lp=000025a8) retval=00000572
: trace:relay:WINPROC_CallWndProc (wndproc=0x2867b260,hwnd=000025a8,msg=WM_PAINT,wp=00000000,lp=00000000) retval=00000000
: trace:relay:WINPROC_CallWndProc (wndproc=0x4a4a3d,hwnd=00000138,msg=WM_ENTERIDLE,wp=00000000,lp=00000a14)
: Call user32.132: DefFrameProcA(00000138,000003ac,00000121,00000000,00000a14) ret=004a5e61 fs=008f
: Ret  user32.132: DefFrameProcA() retval=00000000 ret=004a5e61 fs=008f
: trace:relay:WINPROC_CallWndProc (wndproc=0x4a4a3d,hwnd=00000138,msg=WM_ENTERIDLE,wp=00000000,lp=00000a14) retval=00000000

: ... and got no clue to what they mean!

This call doesn't seem to be the culprit. Go up the log and look where some
input is requested by the program

Bye

-- 
Uwe Bonnes                bon at elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------