From: Daniel Jacobowitz <drow@false.org>
To: Frank Meerkoetter <frank@betaversion.net>
Cc: gdb@sourceware.org
Subject: Re: multithreaded programs on arm-linux
Date: Fri, 04 Nov 2005 15:40:00 -0000 [thread overview]
Message-ID: <20051104154042.GB4309@nevyn.them.org> (raw)
In-Reply-To: <20051104163930.rubgkjl3v0hwgw8o@admin.betaversion.net>
On Fri, Nov 04, 2005 at 04:39:30PM +0100, Frank Meerkoetter wrote:
> Quoting Daniel Jacobowitz <drow@false.org>:
>
> >On Fri, Nov 04, 2005 at 10:23:21AM +0100, Frank Meerkoetter wrote:
> >>Quoting Daniel Jacobowitz <drow@false.org>:
> >>
> >>>On Thu, Nov 03, 2005 at 06:50:47PM +0100, Frank Meerkoetter wrote:
> >>>>objfile is NULL, why i couldn't figure out.
> >>>
> >>>That should be true the first time but not the second, if you've used
> >>>"file".
> >>
> >>Ok. The first time objfile is null. The second time target_has_execution
> >>is false.
> >
> >It doesn't get called after you say "run"? Is this a static executable
> >you're debugging?
>
> It does get called. Sorry, i tested the wrong thing.
>
> [...]
> /* Now attempt to open a connection to the thread library. */
> err = td_ta_new_p (&proc_handle, &thread_agent);
>
> It returns TD_NOLIBTHREAD.
>
> I know from stepping through thread_db_load() that
> That td_ta_new_p = verbose_dlsym (handle, "td_ta_new");
> was successfull.
>
> verbose_dlsym() also produced now warning that it couldn't
> find a certain symbol.
>
> td_ta_new seems to fail.
> I've downloaded the linuxThreads source but can't find any
> references to "td_ta_new".
It's in libthread_db, which is linuxthreads_db/ in the LinuxThreads
source.
It sounds like your libpthread.so has been stripped of some required
symbols.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-04 15:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:11 frank
2005-11-01 18:22 ` Daniel Jacobowitz
2005-11-02 8:00 ` frank
2005-11-02 12:36 ` Andreas Schwab
2005-11-02 12:46 ` frank
2005-11-02 13:28 ` Andreas Schwab
2005-11-02 13:43 ` Daniel Jacobowitz
2005-11-02 14:33 ` Andreas Schwab
2005-11-02 14:39 ` Daniel Jacobowitz
2005-11-02 15:56 ` Frank Meerkoetter
2005-11-02 16:49 ` Daniel Jacobowitz
2005-11-03 8:33 ` Frank Meerkoetter
2005-11-03 13:56 ` Daniel Jacobowitz
2005-11-03 15:00 ` Frank Meerkoetter
2005-11-03 15:07 ` Daniel Jacobowitz
2005-11-03 15:51 ` Frank Meerkoetter
2005-11-03 15:59 ` Daniel Jacobowitz
2005-11-03 16:28 ` Frank Meerkoetter
2005-11-03 16:42 ` Daniel Jacobowitz
2005-11-03 17:51 ` Frank Meerkoetter
2005-11-03 21:13 ` Daniel Jacobowitz
2005-11-04 9:23 ` Frank Meerkoetter
2005-11-04 14:25 ` Daniel Jacobowitz
2005-11-04 15:39 ` Frank Meerkoetter
2005-11-04 15:40 ` Daniel Jacobowitz [this message]
2005-11-04 15:51 ` Frank Meerkoetter
2005-11-04 16:06 ` Frank Meerkoetter
2005-11-04 16:14 ` Daniel Jacobowitz
2005-11-04 15:41 ` Daniel Jacobowitz
2005-11-07 9:26 ` Frank Meerkoetter
2005-11-02 16:52 ` Andreas Schwab
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=20051104154042.GB4309@nevyn.them.org \
--to=drow@false.org \
--cc=frank@betaversion.net \
--cc=gdb@sourceware.org \
/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