winedbg

[Michal Janusz Miroslaw]

Hello,
Is anyone working on winedbg ? I have some ideas and would like to hear
opinions/more ideas/flames:

* enabling/disabling of displays [done]
  * displays shown in one function only [done]
  * implement define command to add symbols on the fly (didn't find it
    is sources except in help text ...)
  * save/restore breakpoints/displays/defined symbols
  * reverse backtrace list (so current frame is at the bottom and you
    dont have to scroll all the way up)
  * remove limit of 10 entries in DEBUG_GetSymbolValue [done]
  * remove duplicated code in DEBUG_FindNearestSymbol/DEBUG_CheckLinenoStatus

I haven't looked everywhere, yet, but `grep FIXME *|wc -l` shows 106 now,
so I should find something. :)

-- Michal Miroslaw

[Michal Janusz Miroslaw]

I forgot to say this in my last mail:

You can download the patch against current CVS from:
http://mion.elka.pw.edu.pl/~mmirosla/winedbg.diff

(It's 30kB, and growing ;)

-- Michal Miroslaw

[Eric Pouech]

> Is anyone working on winedbg ? I have some ideas and would like to hear
> opinions/more ideas/flames: >

see below for the overall idea
> - enabling/disabling of displays [done]
> - displays shown in one function only [done]

ok for those (basically, it's needed if you implement gdb behavior of 
disabling a display if we fail to evaluate it at some point)
> - implement define command to add symbols on the fly (didn't find it
> is sources except in help text ...)

symbolfile/DEBUG_ReadSymbolTable does this job
> - save/restore breakpoints/displays/defined symbols

source/DEBUG_Parser allows to set bp from text files
> - reverse backtrace list (so current frame is at the bottom and you
> dont have to scroll all the way up)
> - remove limit of 10 entries in DEBUG_GetSymbolValue [done]
> - remove duplicated code in DEBUG_FindNearestSymbol/DEBUG_CheckLinenoStatus
> I haven't looked everywhere, yet, but `grep FIXME *|wc -l` shows 106 now,
> so I should find something. :)

I don't think we should spend too much time enhancing winedbg.

doing the same grep for FIXME just in wine/dlls sub dirs spits out about 
6500 FIXMEs... so we'd better spend some time on those which are really 
needed

moreover, the --gdb option deprecates most of the extension you're 
looking at (I even wonder if we shouldn't set --gdb as default way to 
run winedbg, and to have a specific command line options for the current 
debugger)

A+

[Ove Kaaven]

fre, 18.04.2003 kl. 20.13 skrev Eric Pouech:
> moreover, the --gdb option deprecates most of the extension you're 
> looking at (I even wonder if we shouldn't set --gdb as default way to 
> run winedbg, and to have a specific command line options for the current 
> debugger)

Can you see backtraces for other threads than the current (the one that
crashed) from gdb yet with that code? If not, --gdb is almost useless,
most of the problems I've had that --gdb might have solved have been
multithreaded. I once took a look but the code didn't spell out anything
like "implement this to be able to read the registers of other threads"
either, do you have a plan for it?

[Eric Pouech]

> Can you see backtraces for other threads than the current (the one that
> crashed) from gdb yet with that code? 
> If not, --gdb is almost useless,
> most of the problems I've had that --gdb might have solved have been
> multithreaded. I once took a look but the code didn't spell out anything
> like "implement this to be able to read the registers of other threads"
> either, do you have a plan for it?

well, I'm working on a fix. should be ready RSN
A+