[uClibc] Missing corrupt debug information on powerpc

Andrew de Quincey adq_dvb at lidskialf.net
Fri Nov 5 09:48:49 UTC 2004


Hi - I'm using a uclibc snapshot as of 28th October, with gcc 3.3.4, compiled 
using the toolchain builder from that date in CVS. It is configured as a 
crosscompiler from i386->ppc-405. Normal usage of programs on the remote 
machine works fine. Except for debugging:

e.g. on the build machine:

sh-2.05a# ppc-405-linux-gcc -g test.c
sh-2.05a# ppc-405-linux-objdump -g a.out

a.out:     file format elf32-powerpc

ppc-405-linux-objdump: a.out: no recognized debugging information


I can see there is definitely debugging information in the file using hexdump 
- oh and the correct sections are there.


On the target, gdb fails to display any symbols at all, making debugging 
impossible.

The sample program above is:
#include <stdio.h>
#include <stdint.h>

int main(int argc, char* argv[])
{
   int64_t sum;
   int x;
   int y;

   sum = -2000;
   x = atoi(argv[1]);

   printf("%lli\n", sum >> x);

}

uclibc on the target is compiled without debug symbols and is stripped. a.out 
is NOT stripped.

Anyone have any suggestions?



More information about the uClibc mailing list