This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Static application with --dynamic-list crashes
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: <nd at arm dot com>, Alexey Neyman <stilor at att dot net>, <libc-alpha at sourceware dot org>
- Date: Wed, 15 Mar 2017 09:34:25 +0000
- Subject: Re: Static application with --dynamic-list crashes
- Authentication-results: sourceware.org; auth=none
- Authentication-results: sourceware.org; dkim=none (message not signed) header.d=none;sourceware.org; dmarc=none action=none header.from=arm.com;
- Nodisclaimer: True
- References: <f497daa8-3fc5-2d80-023e-79be46d5bf52@att.net> <mvmbmt2ykxq.fsf@hawking.suse.de> <58C9074A.8090001@arm.com> <mvm1styyjje.fsf@hawking.suse.de>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 15/03/17 09:29, Andreas Schwab wrote:
> On Mär 15 2017, Szabolcs Nagy <szabolcs.nagy@arm.com> wrote:
>
>> On 15/03/17 08:59, Andreas Schwab wrote:
>>> On Mär 15 2017, Alexey Neyman <stilor@att.net> wrote:
>>>
>>>> when a gdbserver is linked statically,
>>>
>>> Why are you doing that?
>>>
>>
>> it is useful for debugging a system
>> with broken libc and ssh access only
>> (so gdbserver does not work)
>
> Why does it help if it needs it anyway?
>
static linked gdb does not need libc
that's the point