They key in user.reg that controls whether winedbg pops up in its own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1.
The reason I need this is because when my app crashes, the backtrace is so long (~40 frames) that I can only see the bottom (mostly useless half). Is there a way to increase the size of the winedbg window, pause bt's output (like piping to more in a shell), or display only part of a back trace?
-Steve
Same issue here.
--- steve.lustbader@philips.com a écrit : > They key in user.reg that controls whether winedbg pops up in its
own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1.
The reason I need this is because when my app crashes, the backtrace is so long (~40 frames) that I can only see the bottom (mostly useless half). Is there a way to increase the size of the winedbg window, pause bt's output (like piping to more in a shell), or display only part of a back trace?
-Steve
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
At 20.15 07/11/2002 +0100, Sylvain Petreolle wrote:
Same issue here.
I did it this way: - right click on the winedbg window - choose Properties - go to the Configuration tab - specify a value for the Height of the Buffer zone somewhere in the 1000 range (1000 rows/25 should give you 40 pages of memory that you can browse using the scrollbar) - press OK - specify you want this setting to be always used for this application
and you are done
Alberto
--- steve.lustbader@philips.com a écrit : > They key in user.reg that controls whether winedbg pops up in its
own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1.
The reason I need this is because when my app crashes, the backtrace is so long (~40 frames) that I can only see the bottom (mostly useless half). Is there a way to increase the size of the winedbg window, pause bt's output (like piping to more in a shell), or display only part of a back trace?
-Steve
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On November 7, 2002 02:15 pm, Sylvain Petreolle wrote:
Same issue here.
Please checkout this thread: http://www.winehq.com/hypermail/wine-devel/2002/10/index.html#422
steve.lustbader@philips.com a écrit :
They key in user.reg that controls whether winedbg pops up in its own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1.
are you sure you're not editing by hand the registry while the wineserver is still running ? if you do so, wineserver will override your changes when it exits
see Alberto post for setting a larger window A+
-
Alberto Massari -
Dimitrie O. Paun -
Eric Pouech -
steve.lustbader＠philips.com -
Sylvain Petreolle