Am I just doing this wrong or is it a bug?
I am trying to figure out a problem in an application. I want to turn on reg and relay once I am into the program. (If they are turned on initially I can't get into the program because of some sort of timeout or something).
I am following the instructions in the Wine Developer's Guide. I start the program itself in one terminal and get past the timeout-critical bit. In another terminal I start winedbg, use info process to find the id (there are three processes by this point), and attach to the process. I can now do things like info share info regs etc. c/Ctrl-C Each time I get the Wine-dbg> prompt If I type set + reg <return> the debugger seems to sort of hang. It doesn't give the prompt. As time passes it complains about being not able to find rhe pdb files etc. but at no point do I get the opportunity to tell it to continue. I have tried leaving it for 10 minutes after the last pdb complaint but still no success. Am I supposed to get a prompt?
Bill Medland a écrit :
Am I just doing this wrong or is it a bug?
I am trying to figure out a problem in an application. I want to turn on reg and relay once I am into the program. (If they are turned on initially I can't get into the program because of some sort of timeout or something).
I am following the instructions in the Wine Developer's Guide. I start the program itself in one terminal and get past the timeout-critical bit. In another terminal I start winedbg, use info process to find the id (there are three processes by this point), and attach to the process. I can now do things like info share info regs etc. c/Ctrl-C Each time I get the Wine-dbg> prompt If I type set + reg <return> the debugger seems to sort of hang. It doesn't give the prompt. As time passes it complains about being not able to find rhe pdb files etc. but at no point do I get the opportunity to tell it to continue. I have tried leaving it for 10 minutes after the last pdb complaint but still no success. Am I supposed to get a prompt?
it normally takes some time as the way it's coded now, winedbg will have to load debug info for most of the DLLs before being able to do the first set +/- operation. So, after some time (20 seconds or so on my machine), you get back the prompt. Could rerun with WINEDEBUG="+dbghelp,+winedbg" and post the output ? A+
On October 15, 2004 10:35 am, Eric Pouech wrote: (Thanks for the response)
Bill Medland a écrit :
Am I just doing this wrong or is it a bug?
Snip
If I type set + reg <return> the debugger seems to sort of hang. It doesn't give the prompt. As time passes it complains about being not able to find rhe pdb files etc. but at no point do I get the opportunity to tell it to continue. I have tried leaving it for 10 minutes after the last pdb complaint but still no success. Am I supposed to get a prompt?
it normally takes some time as the way it's coded now, winedbg will have to load debug info for most of the DLLs before being able to do the first set +/- operation. So, after some time (20 seconds or so on my machine), you get back the prompt. Could rerun with WINEDEBUG="+dbghelp,+winedbg" and post the output ? A+
The issue is now a little irrelevant; I have a tiny program that fails to run in the same way as the big one. Do you want to carry on looking into this to find out what is wrong in the winedbg or were you just offering to help me out? If you want to investigate the winedbg failure I can post something (it will probably be big) but otherwise I suggest we drop it (and we can move on to the next problem)
If I type set + reg <return> the debugger seems to sort of hang. It doesn't give the prompt. As time passes it complains about being not able to find rhe pdb files etc. but at no point do I get the opportunity to tell it to continue. I have tried leaving it for 10 minutes after the last pdb complaint but still no success. Am I supposed to get a prompt?
it normally takes some time as the way it's coded now, winedbg will have to load debug info for most of the DLLs before being able to do the first set +/- operation. So, after some time (20 seconds or so on my machine), you get back the prompt. Could rerun with WINEDEBUG="+dbghelp,+winedbg" and post the output ? A+
The issue is now a little irrelevant; I have a tiny program that fails to run in the same way as the big one. Do you want to carry on looking into this to find out what is wrong in the winedbg or were you just offering to help me out? If you want to investigate the winedbg failure I can post something (it will probably be big) but otherwise I suggest we drop it (and we can move on to the next problem)
my post was related you 'set + reg' hanging 'for no reason', not why your program was failing. The WINEDEBUG thingie is just to pinpoint where the hanging may take place. A+
-
Bill Medland -
Eric Pouech