Thread overview | ||||||
---|---|---|---|---|---|---|
|
July 21, 2004 WinDbg 6.3 ? | ||||
---|---|---|---|---|
| ||||
I downloaded free digital mars compiler 8.40c command line version and wondering if someone has experience with using it with windbg ? It's strange but with current windbg 6.3 version i can debug program but cannot show any local variables or watch (new debug symbols version?). I try to make simple hello.c like online help suggested with command line: dmc -g hello.c Debug with Windbg is OK but still I cannot inspect any variables becouse of this error: ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: k *** *** *** ************************************************************************* Another problem with local variables is 0:000> dv Unable to enumerate locals, Win32 error 50 Private symbols (symbols.pri) are required for locals. Type ".hh dbgerr005" for details. I know that it's not strictly related to Digital Mars but any help is really appreciated as windbg is the only free debugger available for digital mars as i know. Maybe old version of windbg is working better with Digital Mars ? Where can i find any info about working with windbg and Digital Mars ? Any other free symbolic debuggers for Digital Mars (console version is ok)? -- Best Regards Bogusław Brandys -- Best Regards Bogusław Brandys -- |
July 21, 2004 Re: WinDbg 6.3 ? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Boguslaw Brandys | Short answer: Don't use Windbg. Purchase the CD and use the IDE's debugger.
Another option you might look into, because it's free as in software but not as in beer, is hacking the GNU libbfd (part of GDB) to understand COFF/OMF files (actually, it most likely does since I wrote some of the code waaaay back in a previous lifetime to support SCO Unix and Xenix.) You might need to do a recompile or two... and you might have to update the name mangling scheme, if it's not supported already.
-scooter
Boguslaw Brandys wrote:
> I downloaded free digital mars compiler 8.40c command line version and wondering if someone has
> experience with using it with windbg ?
> It's strange but with current windbg 6.3 version i can debug program but cannot show any local
> variables or watch (new debug symbols version?).
>
> I try to make simple hello.c like online help suggested with command line:
>
> dmc -g hello.c
>
> Debug with Windbg is OK but still I cannot inspect any variables
> becouse of this error:
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: k ***
> *** ***
> *************************************************************************
>
> Another problem with local variables is
>
> 0:000> dv
> Unable to enumerate locals, Win32 error 50
> Private symbols (symbols.pri) are required for locals.
> Type ".hh dbgerr005" for details.
>
> I know that it's not strictly related to Digital Mars but any help is really appreciated as
> windbg is the only free debugger available for digital mars as i know.
> Maybe old version of windbg is working better with Digital Mars ?
> Where can i find any info about working with windbg and Digital Mars ? Any other free symbolic
> debuggers for Digital Mars (console version is ok)?
>
>
>
>
> --
> Best Regards
> Bogusław Brandys
|
July 22, 2004 Re: WinDbg 6.3 ? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Scott Michel | Thank You.I saw ide in action but I don't like the way IDE is working (of course this is my personal feeling) I would try to extract internal codeview into PDB if it is possible. Best Regards Boguslaw Dnia Wed, 21 Jul 2004 12:02:40 -0700, Scott Michel <scottm@aero.org> napisał: > Short answer: Don't use Windbg. Purchase the CD and use the IDE's debugger. > > Another option you might look into, because it's free as in software but not as in beer, is hacking the GNU libbfd (part of GDB) to understand COFF/OMF files (actually, it most likely does since I wrote some of the code waaaay back in a previous lifetime to support SCO Unix and Xenix.) You might need to do a recompile or two... and you might have to update the name mangling scheme, if it's not supported already. > > > -scooter > > Boguslaw Brandys wrote: > >> I downloaded free digital mars compiler 8.40c command line version and wondering if someone has >> experience with using it with windbg ? >> It's strange but with current windbg 6.3 version i can debug program but cannot show any local >> variables or watch (new debug symbols version?). >> I try to make simple hello.c like online help suggested with command line: >> dmc -g hello.c >> Debug with Windbg is OK but still I cannot inspect any variables >> becouse of this error: >> ************************************************************************* >> *** *** >> *** *** >> *** Your debugger is not using the correct symbols *** >> *** *** >> *** In order for this command to work properly, your symbol path *** >> *** must point to .pdb files that have full type information. *** >> *** *** >> *** Certain .pdb files (such as the public OS symbols) do not *** >> *** contain the required information. Contact the group that *** >> *** provided you with these symbols if you need this command to *** >> *** work. *** >> *** *** >> *** Type referenced: k *** >> *** *** >> ************************************************************************* >> Another problem with local variables is >> 0:000> dv >> Unable to enumerate locals, Win32 error 50 >> Private symbols (symbols.pri) are required for locals. >> Type ".hh dbgerr005" for details. >> I know that it's not strictly related to Digital Mars but any help is really appreciated as >> windbg is the only free debugger available for digital mars as i know. >> Maybe old version of windbg is working better with Digital Mars ? >> Where can i find any info about working with windbg and Digital Mars ? Any other free symbolic >> debuggers for Digital Mars (console version is ok)? >> -- Best Regards >> Bogusław Brandys -- Używam programu pocztowego wbudowanego w Operę: http://www.opera.com/m2/ |
July 22, 2004 Re: WinDbg 6.3 ? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Boguslaw Brandys | Boguslaw Brandys wrote:
> Thank You.I saw ide in action but I don't like the way IDE is working (of course this is my personal feeling)
> I would try to extract internal codeview into PDB if it is possible.
>
> Best Regards
> Boguslaw
The Symantec/Zortech/DMC IDE does show its age a little, but it's still a pretty decent IDE. I've been hacking at a DMC toolchain plug-in for Eclipse with some success (but not as much as I'd like with managed build projects.)
OTOH, if you're willing to work with GDB (Cygwin), you could make that work for you. Extracting codeview data into a PDB file may or may not work. If you do manage to come up with something, post it here too. I'd be somewhat interested.
-scooter
|
Copyright © 1999-2021 by the D Language Foundation