Re: Debugging issue with gdbserver and a daemon on the target

Pedro Alves
2014-08-20T08:17:30Z

On 08/19/2014 07:01 PM, Laszlo Papp wrote:

> Hmm, it seems that the stripped binary on the target and the one on
> the host were out-of-sync. This is really strange since I have not
> changed the source code. Seems different compilations still can get
> out-of-sync for the same code so that when I rebuild the same source
> code, I always need to update the binary on the target, too?

Ideally, if you used the exact same inputs, and the exact same tools,
and the same exact same tool options, the output is the same. You
can check that with md5sum, or some such.

>
> Anyway, now I only have problems with finding the sources file to view
> them in cgdb. I do not know why it is wrong, but it seems to be. As
> you can see the paths are set up for dwarf correctly:
>
> /usr/src/debug/foo-git/AUTOINC+0c2cbe33e653afa335ca25156d293552001228fa-r0/git/meh
>
> ... yet, gdb says src/bar.c cannot be found even though it should be
> in the aforementioned
> /usr/src/debug/foo-git/AUTOINC+0c2cbe33e653afa335ca25156d293552001228fa-r0/git/meh
> path, provided my sysroot setting is good above, but if that was not
> good, it would not load the binaries anyway, right?

Correct.

> So, if I set that
> path one line above with the "-d" option to gdb, then the source file
> can be viewed. What may be going on here?

That sounds like the expected behavior, as the source directory knobs
are independent from the sysroot setting. See:

https://sourceware.org/gdb/current/onlinedocs/gdb/Source-Path.html

> Thanks in advance. I am so desperately lost. :(

I think I'm lost on which part you are lost. :-)

Thanks,
Pedro Alves