From: Albert Antony <albert@newtec.dk>
To: ptxdist@pengutronix.de, Juergen Borleis <jbe@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] Enable "strip" install option handling for libraries
Date: Wed, 22 Jul 2015 10:31:45 +0200 [thread overview]
Message-ID: <CAHChq8MrUGOOEK-d7bWKARC=cxtJRtooUefQA5oyiOiGBnXd4A@mail.gmail.com> (raw)
In-Reply-To: <201507211634.42290.jbe@pengutronix.de>
Hi Juergen,
I am aware of the root-debug option, and indeed that is what we use
for in-house debugging. But we would like to be able to debug a target
that is out in the field, with only ssh access available to it. Having
an unstripped version of the application of interest makes the
debugging a lot easier in this case.
The intention here is not change PTXdist's current behaviour. Existing
build scripts should rightly continue to function as they used to.
What is proposed in the patch is an optional parameter that makes it
possible to install unstripped binaries for libraries. Since
install_copy and install_copy_toolchain_usr already support such an
option, it seemed like a natural extension to have install_lib and
install_copy_toolchain_lib support it as well.
Cheers,
Albert.
On 21 July 2015 at 16:34, Juergen Borleis <jbe@pengutronix.de> wrote:
> Hi Albert,
>
> On Tuesday 21 July 2015 16:03:36 Albert Antony wrote:
>> On 21 July 2015 at 15:14, Juergen Borleis <jbe@pengutronix.de> wrote:
>> > Why do you want to have libraries *with* debug information in your root
>> > filesystem?
>>
>> It just facilitates easier debugging in our case. We can run gdb on
>> the target directly, instead of via gdbserver.
>>
>> Given that this may apply to other users as well, would it not be a
>> good idea to let the user have the choice of installing certain select
>> unstripped binaries in the rootfs if they so desire? Of course the
>> default option would still be to install stripped binaries. Let me
>> know what you think.
>
> As an alternative to change PTXdist's behaviour you could mount the content
> of "platform-<yourplatform>/root-debug" instead and have all debug information
> available on the target.
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K. | Juergen Borleis |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-22 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 12:04 Albert Antony
2015-07-21 13:14 ` Juergen Borleis
2015-07-21 14:03 ` Albert Antony
2015-07-21 14:34 ` Juergen Borleis
2015-07-22 8:31 ` Albert Antony [this message]
2015-07-22 9:29 ` Juergen Borleis
2015-07-22 13:28 ` Albert Antony
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 10:09 Albert Antony
2015-07-21 10:26 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHChq8MrUGOOEK-d7bWKARC=cxtJRtooUefQA5oyiOiGBnXd4A@mail.gmail.com' \
--to=albert@newtec.dk \
--cc=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox