This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Using ddd debugger on OMAP3530

Expert 4920 points
Other Parts Discussed in Thread: OMAP3530

Hello,

I'm a newbie to Linux and the OMAP3530 and am trying to debug a simple 'hello world' program (with an additional dummy function called check( ) )on my Mistral OMAP3530 target using the ddd debugger. Here are the steps I'm following:

- Copy ‘gdbserver’ to ~/workdir/filesys/usr/bin

- Build ‘hello.c’ as ‘arm-none-linux-gnueabi-gcc –c –g –o hello.o hello.c

- Restart EVM

- Run ‘gdbserver 192.168.1.100:1000 hello’ from ~/workdir/filesys/opt/hello/hello.o

- On host run ‘ddd –debugger arm-none-linux-gnueabi-gdb ~/workdir/filesys/opt/hello/hello.o

- (gdb) b main

- (gdb) b check

- (gdb) target remote 192.168.1.10:1000

warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x400007c0 in ?? ( )

- (gdb) cont

warning: .dynamic section for "/lib/libc.so.6" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections:

/lib/ld-linux.so.3: No such file or directory

 

I wasn't sure what these warnings are about and would appreciate any guidance if I need to make any changes to avoid these issues.

 

Thanks!!