significance of strip -g versus strip for remote debugging using gdb/gdbserver

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

significance of strip -g versus strip for remote debugging using gdb/gdbserver

amit.chaudhuri
Hi,


In the context of debugging using gdb on a host to debug a remote target using gdbserver...


If I compare ELF objects prepared with strip -g and strip, I can see that the difference is that the more aggressive option removes debug info AND the symbol table and it's associated string table.

It is clear that this will take up less size on the remote target. But does the presence of the symbol table on the target alter the conversation or speed of operation between gdb/gdbserver?


Regards,


Amit
Reply | Threaded
Open this post in threaded view
|

Re: significance of strip -g versus strip for remote debugging using gdb/gdbserver

Simon Marchi-4
On 2017-11-29 06:00 AM, [hidden email] wrote:

> Hi,
>
>
> In the context of debugging using gdb on a host to debug a remote target using gdbserver...
>
>
> If I compare ELF objects prepared with strip -g and strip, I can see that the difference is that the more aggressive option removes debug info AND the symbol table and it's associated string table.
>
> It is clear that this will take up less size on the remote target. But does the presence of the symbol table on the target alter the conversation or speed of operation between gdb/gdbserver?
>
>
> Regards,
>
>
> Amit
>


Hi Amit,

From what I know, gdbserver doesn't use debug info nor the symbol table of
the executable, so it won't change anything.

Simon