For GUI .pdb debugging I have made some attempts to run Winedbg directly
under KDevelop. As KDevelop Just pushes commands into gdb's stdin and in
return parses stdout, With some relaxing of the parser code, I was able
to get the stack frame and disassembly windows. This is do to the fact
that
Eric Pouech wrote:
that didn't change. This would require gdb to know about .pdb, which
it doesn't. in the long run, it may be easier to get windbg handle
properly elf/{stabs|dwarf} information, rather than the other way around.
A+
From passed experience, I have found that for Winelib, or P
Boaz Harrosh wrote:
Eric Pouech wrote:
- in my case, the source code doesn't show up alone. I use the 'show
code' button in the breakpoint window
Is that gcc-elf-Linux code only like before? or is it possible now to,
also see PE (.pdb) debugging info?
that didn't change. This would require
Eric Pouech wrote:
- in my case, the source code doesn't show up alone. I use the 'show
code' button in the breakpoint window
Is that gcc-elf-Linux code only like before? or is it possible now to,
also see PE (.pdb) debugging info?
Thanks Boaz
Markus Gömmel wrote:
Hi,
I'm coming from Windows, so a graphical debugging system is needed :-)
I'm trying to connect winedbg to ddd as described in the docu, but the
following error occured during startup:
wine-pthread: gdbproxy.c:1984: extract_packets: Assertion 'i ==
gdbctx->out_len' fai
Hi,
I'm coming from Windows, so a graphical debugging system is needed :-)
I'm trying to connect winedbg to ddd as described in the docu, but the
following error occured during startup:
wine-pthread: gdbproxy.c:1984: extract_packets: Assertion 'i ==
gdbctx->out_len' failed.
Same happens when
