2007/3/29, Dennis Schridde devurandom@gmx.net:
Am Donnerstag, 29. März 2007 schrieb Eric Pouech:
Dennis Schridde a écrit :
Hello Wine users!
I've got a minidump from a ("real") Windows user of our game and would like to extract information from it using winedbg.
The information winedbg gives me by default, is this:
[...]
Which is pretty rare. Via addr2line I can translate the backtrace to possibly valid
locations
in our sourcefiles.
My questions are:
- Why doesn't winedbg extract the sourcecode locations itself?
because it needs the original PE files (.exe, .dll) to get to the debug information those files must be seated in directories listed in the _NT_SYMBOL_PATH environment variable
Maybe I am just doing it wrong, but _NT_SYMBOL_PATH=. winedbg warzone2100.mdmp doesn't change anything... (Even supplying the full path doesn't.) The exe (not all dlls, because I don't have a copy of the user's system) is of course in the working directory.
But the debug info is not always in the .exe itself. the .exe can contain only a pointer to the debug info what does 'winedbg -x debug -g warzone2100.exe' give ?
- Why doesn't winedbg show me the other information included in the
minidump, like the loaded modules, commandline options or version information?
'info share' should do part of it... winedbg doesn't show the command line info nor options
That only shows me the memory ranges of some modules. The minidump includes more info, like the paths to dlls and similar. I am not sure whether it includes version information, but it certainly contains the commandline used to start the app.
other thing you can do is to use winedump (man winedump)
How do I do this? And what will it provide? I tried winedump -G warzone2100.exe but I have no idea what I shall do with that tremedously long and cryptic list.
winedump warzone2100.mdmp
- How can I get the parameters to the last called function(s)?
see above for debug info
If the general debug info worked, that would also show me the function parameters?
yes