RFE: Actually I am not interested in debug msgs after the debugger started. Could there be an option that an debugger start turns off debug msgs.
set - all
When the debugger starts I often get the msg wine: hash.c:392: DEBUG_GetSymbolValue: Assertion 'strlen(name) < sizeof(buffer) - 2' failed. which results in an unhandled exception in the debugger. Whats up with that?
fixed size for internal buffers... however a 512 characters identifier seems a bit big to me (even in C++) would you mind printing out the name of the symbol, just to check I'll send a work around for that
A+
On Tuesday 05 November 2002 20:29, Eric Pouech wrote:
RFE: Actually I am not interested in debug msgs after the debugger started. Could there be an option that an debugger start turns off debug msgs.
set - all
the debugger is called on an unhandled exception the debugger call in the AeDebug registry key has --debugmsg -all set but after wine prints the unhandled exception line and calls the debugger there is still a lot of debug output after that
When the debugger starts I often get the msg wine: hash.c:392: DEBUG_GetSymbolValue: Assertion 'strlen(name) < sizeof(buffer) - 2' failed. which results in an unhandled exception in the debugger. Whats up with that?
fixed size for internal buffers... however a 512 characters identifier seems a bit big to me (even in C++) would you mind printing out the name of the symbol, just to check I'll send a work around for that
A+
I tried the workaround cause it prints out the symbols name but no symbol name was forthcoming. on the other hand the unhandled exception in the debugger is gone too so it wasnt all in vain. in debugger window there is a lot of gibberish shown like Unknown type '#' or Unknown type '&' and a lot of very long failure on blah blah blah prints that span multiple lines.is that what you mean?
Enrico Horn a écrit :
On Tuesday 05 November 2002 20:29, Eric Pouech wrote:
RFE: Actually I am not interested in debug msgs after the debugger started. Could there be an option that an debugger start turns off debug msgs.
set - all
the debugger is called on an unhandled exception the debugger call in the AeDebug registry key has --debugmsg -all set but after wine prints the unhandled exception line and calls the debugger there is still a lot of debug output after that
set - all is a debugger command. beware also that --debugmsg -all option when starting winedbg will turn on debug message for the winedbg process, it won't turn them off for the process you're debugging. 'set - all' command will
I tried the workaround cause it prints out the symbols name but no symbol name was forthcoming.
you must turn on printing for the warn channel message.
in debugger window there is a lot of gibberish shown like Unknown type '#' or Unknown type '&' and a lot of very long failure on blah blah blah prints that span multiple lines.is that what you mean?
are you still debugging a windows app ? normally those messages come out while loading an ELF module, compiled as a C++ module as wine (and all it's component) is only compiled as C, I don't get where all these come wrong (unless your windows program is C++ and has been compiled with mingw)
A+
On Wednesday 06 November 2002 21:25, you wrote:
Enrico Horn a écrit :
On Tuesday 05 November 2002 20:29, Eric Pouech wrote:
RFE: Actually I am not interested in debug msgs after the debugger started. Could there be an option that an debugger start turns off debug msgs.
set - all
the debugger is called on an unhandled exception the debugger call in the AeDebug registry key has --debugmsg -all set but after wine prints the unhandled exception line and calls the debugger there is still a lot of debug output after that
set - all is a debugger command. beware also that --debugmsg -all option when starting winedbg will turn on debug message for the winedbg process, it won't turn them off for the process you're debugging. 'set - all' command will
doesnt seems to save this setting between debugger calls so its of no use to me. why does it turn the debug msgs on when i say --debugmsg -all !?!
I tried the workaround cause it prints out the symbols name but no symbol name was forthcoming.
you must turn on printing for the warn channel message.
been there done that didnt work
in debugger window there is a lot of gibberish shown like Unknown type '#' or Unknown type '&' and a lot of very long failure on blah blah blah prints that span multiple lines.is that what you mean?
are you still debugging a windows app ? normally those messages come out while loading an ELF module, compiled as a C++ module as wine (and all it's component) is only compiled as C, I don't get where all these come wrong (unless your windows program is C++ and has been compiled with mingw)
dont know what kind of app it is, since these lines appear before winedbg says it loaded debug info from /usr/X11R6/lib/libGLU.so.1 i assume its coming from this library. this is mesa 4.0.3 on my system
Enrico farmboy1@subdimension.com
doesnt seems to save this setting between debugger calls so its of no use to me. why does it turn the debug msgs on when i say --debugmsg -all !?!
that is effectively broken... I'll look into it
dont know what kind of app it is, since these lines appear before winedbg says it loaded debug info from /usr/X11R6/lib/libGLU.so.1 i assume its coming from this library. this is mesa 4.0.3 on my system
ok, this lib is in fact C++ and it explains why winegdb prints out this unknown type messages (winedbg is too verbose here) A+
-
Enrico Horn -
Eric Pouech