Hi,
For the past week or so winedbg has refused to start, it just hangs whenever it tries to attach to a pid.
Some traces indicate it's getting an access denied error when trying to attach? Not sure why i'd be getting that. I thought it was just my tree at first but Splinter on IRC says he has the same problem.
Does anybody else see this?
On Mon, Apr 14, 2003 at 11:51:24PM +0100, Mike Hearn wrote:
Hi,
For the past week or so winedbg has refused to start, it just hangs whenever it tries to attach to a pid.
Some traces indicate it's getting an access denied error when trying to attach? Not sure why i'd be getting that. I thought it was just my tree at first but Splinter on IRC says he has the same problem.
Does anybody else see this?
Yep, I have the same problem.
Am Dienstag 15 April 2003 00:51 schrieb Mike Hearn:
Hi,
For the past week or so winedbg has refused to start, it just hangs whenever it tries to attach to a pid.
Some traces indicate it's getting an access denied error when trying to attach? Not sure why i'd be getting that. I thought it was just my tree at first but Splinter on IRC says he has the same problem.
Does anybody else see this?
Hi,
i have started to find the patch that broke winedbg yesterday. Today i can tell you that one of the 4 last patches in March broke winedbg for me.
Bye Stefan
"Stefan" == Stefan Leichter Stefan.Leichter@camLine.com writes:
Stefan> Am Dienstag 15 April 2003 00:51 schrieb Mike Hearn: >> Hi, >> >> For the past week or so winedbg has refused to start, it just hangs >> whenever it tries to attach to a pid. >> >> Some traces indicate it's getting an access denied error when trying >> to attach? Not sure why i'd be getting that. I thought it was just my >> tree at first but Splinter on IRC says he has the same problem. >> >> Does anybody else see this?
Stefan> Hi,
Stefan> i have started to find the patch that broke winedbg Stefan> yesterday. Today i can tell you that one of the 4 last patches Stefan> in March broke winedbg for me.
Check that your [Software\Microsoft\Windows NT\CurrentVersion\AeDebug] is really available in ~/.wine/system.reg.
Otherwise a default string is used that had an error. Patch for the default string just sent to wine-patches
Bye
Am Dienstag 15 April 2003 20:29 schrieb Uwe Bonnes:
"Stefan" == Stefan Leichter Stefan.Leichter@camLine.com writes:
Stefan> Am Dienstag 15 April 2003 00:51 schrieb Mike Hearn: >> Hi, >> >> For the past week or so winedbg has refused to start, it just hangs >> whenever it tries to attach to a pid. >> >> Some traces indicate it's getting an access denied error when trying >> to attach? Not sure why i'd be getting that. I thought it was just >> my tree at first but Splinter on IRC says he has the same problem. >> >> Does anybody else see this? Stefan> Hi, Stefan> i have started to find the patch that broke winedbg Stefan> yesterday. Today i can tell you that one of the 4 last patches Stefan> in March broke winedbg for me.
Check that your [Software\Microsoft\Windows NT\CurrentVersion\AeDebug] is really available in ~/.wine/system.reg.
Otherwise a default string is used that had an error. Patch for the default string just sent to wine-patches
I had this one: [Software\Microsoft\Windows NT\CurrentVersion\AeDebug] 996976720 "Auto"="1" "Debugger"="winedbg.exe --debugmsg -all %ld %ld"
removing the '.exe' and adding --auto did not help. But i found the patch that broke winedbg for me:
http://www.winehq.com/hypermail/wine-cvs/2003/03/0371.html
Bye Stefan
I had this one: [Software\Microsoft\Windows NT\CurrentVersion\AeDebug] 996976720 "Auto"="1" "Debugger"="winedbg.exe --debugmsg -all %ld %ld"
removing the '.exe' and adding --auto did not help. But i found the patch that broke winedbg for me:
Hmm, more of Alexandres deep threading code. I don't really want to unapply that as I have no idea what it does or what its dependancies are.
Alexandre, could you take a look at why this patch might have broken winedbg?
thanks -mike
Stefan Leichter Stefan.Leichter@camLine.com writes:
removing the '.exe' and adding --auto did not help. But i found the patch that broke winedbg for me:
What kernel are you using?
Am Mittwoch 16 April 2003 21:40 schrieb Alexandre Julliard:
Stefan Leichter Stefan.Leichter@camLine.com writes:
removing the '.exe' and adding --auto did not help. But i found the patch that broke winedbg for me:
What kernel are you using?
My system is SuSE 7.3. The kernel rpm is called k_deflt-2.4.16-37. The SuSE kernels are a little away from the standard kernels. You can get the kernel (rpm & source) from:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/kernel/2.4.16-20020416/
Bye Stefan
Stefan Leichter Stefan.Leichter@camLine.com writes:
My system is SuSE 7.3. The kernel rpm is called k_deflt-2.4.16-37.
OK that's a known problem that happens with older 2.4 kernels, I just forgot to merge that fix. It should work now.
Am Donnerstag 17 April 2003 01:38 schrieb Alexandre Julliard:
Stefan Leichter Stefan.Leichter@camLine.com writes:
My system is SuSE 7.3. The kernel rpm is called k_deflt-2.4.16-37.
OK that's a known problem that happens with older 2.4 kernels, I just forgot to merge that fix. It should work now.
Yes, it is ok now
Thanks Stefan