From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Albert Fu <quarkverse@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Program terminated by SIGTRAP in gdb
Date: Fri, 16 Jan 2009 23:34:00 -0000 [thread overview]
Message-ID: <8ac60eac0901161533i1b8dc4ffge184525c1ba0e2c4@mail.gmail.com> (raw)
In-Reply-To: <966c7c700901161513o6bca18dbx5ad35a1924b41130@mail.gmail.com>
[I added gdb@sourceware.org back]
On Fri, Jan 16, 2009 at 3:13 PM, Albert Fu <quarkverse@gmail.com> wrote:
>> Did you do that command on host or on target (or are they one and
>> the same)?
> It produced "No Symbols" when I ran the command on the target.
>
> I guest libpthread.so0 is stripped.
Indeed. I am glad I asked.
> Is there any example to compile a non-stripped version of libpthread?
Your compiled for target version is already likely not stripped.
Possibly you stripped it before copying to target, to save space.
If so, use 'strip --strip-debug' instead of 'strip'.
If your target version is stripped, notify your vendor that
it is "no good".
Rebuilding glibc for target using your cross-compiler will produce
non-stripped version. Beware: libc.so.6, libpthread.so.0,
ld-linux.so.2 etc. etc. must all match! Do not "mix and match"
parts of glibc from different compilations.
Cheers,
--
Paul Pluzhnikov
prev parent reply other threads:[~2009-01-16 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 0:37 Albert Fu
2009-01-15 2:08 ` teawater
2009-01-16 2:06 ` Paul Pluzhnikov
2009-01-16 19:05 ` Albert Fu
2009-01-16 20:13 ` Paul Pluzhnikov
[not found] ` <966c7c700901161513o6bca18dbx5ad35a1924b41130@mail.gmail.com>
2009-01-16 23:34 ` Paul Pluzhnikov [this message]
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=8ac60eac0901161533i1b8dc4ffge184525c1ba0e2c4@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=quarkverse@gmail.com \
/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