[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debug info in debian/ubuntu gnustep-examples

From: Richard Frith-Macdonald
Subject: Re: Debug info in debian/ubuntu gnustep-examples
Date: Thu, 22 Oct 2009 06:11:15 +0100

On 21 Oct 2009, at 19:39, Fred Kiefer wrote:

Eduardo Osorio Armenta schrieb:
Hello GNUstep community

I'm new to this list; First of all great environment/framework/ tools, KUDOS
to all DEVs.

I'm becoming a fan/user of WindowMaker/GNUstep in ubuntu 9.04

I hope you get me a little help/direction/url trying to get the debug
symbols when compiling
the examples from gnustep-examples source in ubuntu package

after downloading the source of this package i compiled fine with
and run with
openapp ApplicationName.app

but trying to debug with gdb, it states that no debug info was know for
every program
so i research in gnustep wiki for a HowTo cook
and found that the command

make messages=yes

That prints verbose output while bulding ... it doesn't build for debugging.
What you want is
make debug=yes

produces this info, but this didn't worked for gnustep-examples programs
only for a simple HelloWorld program (using Foundation NSLog, etc)

As far as I know all GNUstep components get compiled with debug
information enabled.

Yes, but unless you do 'make debug=yes' they are also compiled with optimisation ... which makes it difficult to interpret the output of gdb reliably as the optimiser will change the exact control flow in the program (so the line displayed in gdb can jump about unpredictably) and will remove many variables (so gdb can't examine them).

So for any code you intend to debug using gdb, you should build with 'make debug=yes' which turns off optimisation.

The simplest way to start debuging a GNUstep application is via

debugapp ApplicationName.app

openapp --debug ApplicationName.app

which is what I prefer.

Hope this helps

Discuss-gnustep mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]