• Sean Eskapp (2/2) Feb 06 2011 Are debug symbols compiled with -gc stored in a separate file? Visual St...
• Trass3r (2/4) Feb 06 2011 Nope.
• Robert Clipsham (8/10) Feb 06 2011 I suggest you take a look at VisualD if you're using visual studio, it
• Sean Eskapp (5/12) Feb 06 2011 I'm using VisualD already, but the project is configured using Makefiles...
• Robert Clipsham (8/20) Feb 07 2011 As Trass3r said, you can run the object file through cv2pdb - I've never...

Sean Eskapp <eatingstaples gmail.com> writes:

Are debug symbols compiled with -gc stored in a separate file? Visual Studio
refuses to debug my things, and windbg seems to be remarkably unhelpful.

Trass3r <un known.com> writes:

 Are debug symbols compiled with -gc stored in a separate file? Visual  
 Studio refuses to debug my things

Nope.
Plus you need to use cv2pdb to debug with Visual

Robert Clipsham <robert octarineparrot.com> writes:

On 06/02/11 20:29, Sean Eskapp wrote:
 Are debug symbols compiled with -gc stored in a separate file? Visual Studio
 refuses to debug my things, and windbg seems to be remarkably unhelpful.

I suggest you take a look at VisualD if you're using visual studio, it 
will handle converting debug info so that visual studio can understand 
it, and give you some intellisense.

http://www.dsource.org/projects/visuald

-- 
Robert
http://octarineparrot.com/

Sean Eskapp <eatingstaples gmail.com> writes:

== Quote from Robert Clipsham (robert octarineparrot.com)'s article
 On 06/02/11 20:29, Sean Eskapp wrote:
 Are debug symbols compiled with -gc stored in a separate file? Visual Studio
 refuses to debug my things, and windbg seems to be remarkably unhelpful.

 I suggest you take a look at VisualD if you're using visual studio, it
 will handle converting debug info so that visual studio can understand
 it, and give you some intellisense.
 http://www.dsource.org/projects/visuald

I'm using VisualD already, but the project is configured using Makefiles, and I
don't want to go through the hassle of changing project configs in two
locations.
Is there any way to still get Visual Studio debugging information if it's a
makefile project?

Robert Clipsham <robert octarineparrot.com> writes:

On 06/02/11 22:28, Sean Eskapp wrote:
 == Quote from Robert Clipsham (robert octarineparrot.com)'s article
 On 06/02/11 20:29, Sean Eskapp wrote:
 Are debug symbols compiled with -gc stored in a separate file? Visual Studio
 refuses to debug my things, and windbg seems to be remarkably unhelpful.

 I suggest you take a look at VisualD if you're using visual studio, it
 will handle converting debug info so that visual studio can understand
 it, and give you some intellisense.
 http://www.dsource.org/projects/visuald

 I'm using VisualD already, but the project is configured using Makefiles, and I
 don't want to go through the hassle of changing project configs in two
locations.
 Is there any way to still get Visual Studio debugging information if it's a
 makefile project?

As Trass3r said, you can run the object file through cv2pdb - I've never 
used this though so I can't tell you how to use it. Take a look at 
http://dsource.org/projects/cv2pdb for more information, I guess you 
just need to add another command to your make file.

-- 
Robert
http://octarineparrot.com/