Re: debugging objc difficulties, here: gdl2

[Manuel Guesdon]

Hi,

On Sun, 16 Jan 2005 10:13:12 +0100 Dirk Lattermann <dlatt@alqualonde.de> wrote:

 >| Hello all,
 >| 
 >| I'm always (and since a long time) having difficulties in debugging 
 >| the GNUstep libiraries, on Linux x86. Stepping through them with gdb 
 >| (6.1) shows source code lines in an order unexplicable to me. I doubt 
 >| it comes from compilation optimizations (I'm using gcc 3.4), because 
 >| often, the current instruction jumps backward into the preceding 
 >| function on a single 'n' in gdb. It seems the source files don't match 
 >| the object files. How can gdb show the file location of the source 
 >| files it is using? I'm seeing only the file name without the path 
 >| component.
 >| 
 >| I also observed this:
 >| I built and installed the core libraries without debugging support (is 
 >| this a problem?), and I built and installed the gdl2 libraries and my 
 >| application with and without debugging (make debug=yes [install]). The 
 >| debug version of my application doesn't seem to use the gdl2 debugging 
 >| libraries (without the _d suffix):
[...]
 >| I compiled .app when the _d libs weren't installed yet and .debug 
 >| after they were installed. Now, when re-compiling, both .app and 
 >| .debug use the _d libraries. Is this intended? Displaying the source 
 >| correctly in gdb still doesn't work, however.

For library, this is strange but as far as I remember, you can't 
have debug and non debug framework version at the same 
time.
May be the best way is to remove your usr/GNUstep tree and rebuild 
all with debug=yes so you'll be sure to have coherent things to 
debug.


Manuel