RE: Vital information for anyone debugging setup.exe
Original Message >From: Brian Dessent >Sent: 20 April 2005 10:14 > Dave Korn wrote: > >> Nope, I saw that, but I wanted to fix insight rather than setup, >> because otherwise it's gonna happen again with some other piece of >> software... I'm in the habit of using loadsa debug messages and logging >> them with dbgview or similar, and I don't want to accidentally >> window-bomb myself again sometime in the future. > > Ah. Well if you do figure out how to disable that in insight please > post. As I said I googled but all I found was others complaining about > it with replies saying that you'd have to dig into insight internals to > change it, and I'm not really conversant in tcl/tk. > > Brian Hmm. handle_output_debug_string in gdb/win32-nat.c translates messages received from OutputDebugString into calls to warning (...). Eventually these get translated through gdb/gdbtk/library/interface.tcl :: show_warning (...) into calls to ide_messageBox (in libgui/src/tclmsgbox.c). I think it would probably be best to fix at the gdb layer. Genuine warnings we still do want to pop up a dialog, it's just that debug output shouldn't be treated as debugger warnings, because it isn't. Just commenting out the call to warning would probably work, although that would mean the debug messages didn't get displayed at all; what we really want is for them to come out in the console window. Not quite sure how to make that happen yet.. cheers, DaveK -- Can't think of a witty .sigline today
Re: Vital information for anyone debugging setup.exe
Dave Korn wrote: > Nope, I saw that, but I wanted to fix insight rather than setup, because > otherwise it's gonna happen again with some other piece of software... I'm > in the habit of using loadsa debug messages and logging them with dbgview or > similar, and I don't want to accidentally window-bomb myself again sometime > in the future. Ah. Well if you do figure out how to disable that in insight please post. As I said I googled but all I found was others complaining about it with replies saying that you'd have to dig into insight internals to change it, and I'm not really conversant in tcl/tk. Brian
RE: Vital information for anyone debugging setup.exe
Original Message >From: Brian Dessent >Sent: 20 April 2005 06:29 > Dave Korn wrote: > >> It would probably be easier simpler and quicker to find the messagebox >> call in the insight source (most of which is just tcl/tk scripting after >> all) and comment it out. > > Perhaps you missed my other reply: > >> Heh, you noticed that too... I googled for a way to disable the popups, >> but found nothing. I just comment out the OutputDebugString() call in >> msg() when using insight. > > Comment out that one line and they're gone... > > Brian Nope, I saw that, but I wanted to fix insight rather than setup, because otherwise it's gonna happen again with some other piece of software... I'm in the habit of using loadsa debug messages and logging them with dbgview or similar, and I don't want to accidentally window-bomb myself again sometime in the future. cheers, DaveK -- Can't think of a witty .sigline today
Re: Vital information for anyone debugging setup.exe
Dave Korn wrote: > It would probably be easier simpler and quicker to find the messagebox > call in the insight source (most of which is just tcl/tk scripting after > all) and comment it out. Perhaps you missed my other reply: > Heh, you noticed that too... I googled for a way to disable the popups, > but found nothing. I just comment out the OutputDebugString() call in > msg() when using insight. Comment out that one line and they're gone... Brian
RE: Vital information for anyone debugging setup.exe
Original Message >From: Gary R. Van Sickle >Sent: 19 April 2005 19:05 > [snip] >> >>> Nevertheless I still prefer insight over gdb. >>> You just have to turn off those misdirected dialog popups, which >>> should be logfile entries. >> >> Yes, I kind of deduced that do you know what the syntax >> is to turn them off, by any chance? > > I think he's talking about doing a search-n-replace on the setup source. It would probably be easier simpler and quicker to find the messagebox call in the insight source (most of which is just tcl/tk scripting after all) and comment it out. Actually it should probably be properly removed and sent upstream as a patch. Opening a fresh window per log message is just plain wrong on pretty much any host or target I can imagine. One window with debug messages scrolling up, yes; one window, that blocks execution until it is clicked away, maybe; one window, that simply overwrites it's message with each new debug message as it arrives, ok; but opening window after window after window without limit? Debug messages just don't belong in dialog boxes. cheers, DaveK -- Can't think of a witty .sigline today
RE: Vital information for anyone debugging setup.exe
[snip] > > > Nevertheless I still prefer insight over gdb. > > You just have to turn off those misdirected dialog popups, which > > should be logfile entries. > > Yes, I kind of deduced that do you know what the syntax > is to turn them off, by any chance? I think he's talking about doing a search-n-replace on the setup source. -- Gary R. Van Sickle
RE: Vital information for anyone debugging setup.exe
Original Message >From: Reini Urban >Sent: 18 April 2005 20:14 > Dave Korn schrieb: >>NO! NO!!! NOOOo !!1!!! >> >> FOR GOD'S SAKE WHATEVER YOU DO DON'T USE INSIGHT >> ONLY EVER USE COMMAND-LINE GDB >> AAARRRGRGH MY EYES > > HA! > Do you know how many windows there are by the time that each of three .ini files have been read to the 100% mark? Do you know how slowly each one of those windows closes when there's hundreds of them? I manually clicked away every single one of them because I wasn't sure if I'd be able to reproduce the error or not, so once I'd got it I didn't want to let it go. It was late at night and my judgement may have been impaired by sleep-deprivation! > Nevertheless I still prefer insight over gdb. > You just have to turn off those misdirected dialog popups, which should > be logfile entries. Yes, I kind of deduced that do you know what the syntax is to turn them off, by any chance? ObTopic: Oh, it's time to repost that do-the-dll-last patch again, with more tidyups and generally finalised. Will get to it shortly. cheers, DaveK -- Can't think of a witty .sigline today
Re: Vital information for anyone debugging setup.exe
Dave Korn schrieb: NO! NO!!! NOOOo !!1!!! FOR GOD'S SAKE WHATEVER YOU DO DON'T USE INSIGHT ONLY EVER USE COMMAND-LINE GDB AAARRRGRGH MY EYES HA! Nevertheless I still prefer insight over gdb. You just have to turn off those misdirected dialog popups, which should be logfile entries. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/
Re: Vital information for anyone debugging setup.exe
On Mon, 18 Apr 2005, Dave Korn wrote: > FOR GOD'S SAKE WHATEVER YOU DO DON'T USE INSIGHT > ONLY EVER USE COMMAND-LINE GDB Most likely everyone gets burned by this once. Until they do, advice of the above sort would probably be rather useless. But just in case there *are* people who actually read the documentation, perhaps putting this in the README or on the web page would be a good idea. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
Re: Vital information for anyone debugging setup.exe
Dave Korn wrote: > FOR GOD'S SAKE WHATEVER YOU DO DON'T USE INSIGHT Heh, you noticed that too... I googled for a way to disable the popups, but found nothing. I just comment out the OutputDebugString() call in msg() when using insight. Brian
Vital information for anyone debugging setup.exe
NO! NO!!! NOOOo !!1!!! FOR GOD'S SAKE WHATEVER YOU DO DON'T USE INSIGHT ONLY EVER USE COMMAND-LINE GDB AAARRRGRGH MY EYES ;) cheers, DaveK -- Can't think of a witty .sigline today
