[SOLVED] gdb debug program compiled in another machine

jessCPP · 03-20-2016, 11:51 AM

Hi there!

I want to apologize if this question is very stupid.

I want to debug a program with 'gdb' and the program has been compiled using this instruction in 'gcc':

Code:

gcc -g test.c -o test

Then I copied the executable file to another machine, but gdb can not find the sources. This is the output when I try to set a break point:

Code:

Reading symbols from test...done.
(gdb) break test.c:7
Breakpoint 1 at 0x8048426: file test.c, line 7.
(gdb) start 
Temporary breakpoint 2 at 0x8048426: file test.c, line 7.
Starting program: /home/user/test 

Breakpoint 1, main () at test.c:7
7	test.c: No such file or directory.

Is there a way to see the source code of a program that has been compiled from another machine in gdb?

Or is it mandatory to have the source code in the same machine as gdb?

Thank you very much!

NevemTeve · 03-20-2016, 03:43 PM

Use FTP, NFS, SMB, sftp or scp to transfer the source.

rtmistler · 03-20-2016, 07:23 PM

In this case I'd put the source file on the same machine where you are trying to debug.

There are options for remote debugging using GDBServer, however if you are capable of running GDB directly on your test machine, then do so and also have the sources available right there versus leave them on the compile machine.

I'm not totally sure, but the argument I used is -ggdb versus just -g.

jessCPP · 03-21-2016, 02:16 AM

Hi!

Thank you very much for your response!

I think I will debug using gdb server, because I am not allowed to copy all the sources to the destination machine.

By the way, what is the difference between -ggdb and -g?