From: Frank Meerkoetter <frank@betaversion.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: multithreaded programs on arm-linux
Date: Thu, 03 Nov 2005 08:33:00 -0000 [thread overview]
Message-ID: <20051103093306.qyr5bz57icqo04ck@admin.betaversion.net> (raw)
In-Reply-To: <20051102164925.GA31801@nevyn.them.org>
Quoting Daniel Jacobowitz <drow@false.org>:
> On Wed, Nov 02, 2005 at 04:55:58PM +0100, Frank Meerkoetter wrote:
>> Quoting Daniel Jacobowitz <drow@false.org>:
>>
>> >On Wed, Nov 02, 2005 at 03:33:17PM +0100, Andreas Schwab wrote:
>> >>Daniel Jacobowitz <drow@false.org> writes:
>> >>
>> >>> While this is true, a LinuxThreads library won't require
>> >>> nptl_version...
>> >>
>> >>I was assuming NPTL, because AFAIK LinuxThreads does not have the symbol
>> >>stripping problem (the dynamic symbol table of the library should be good
>> >>enough).
>> >
>> >Oh. Huh - I didn't realize that.
>>
>> Does anyone have an idea left how i could end up with
>> a thread enabled gdb?
>>
>> What steps could i try to narrow down the problem?
>
> How about answering whether you are using NPTL or LinuxThreads first?
Sorry, that was a misunderstanding on my side. I'm running
LinuxThreads.
# uname -a
Linux (none) 2.4.19-rmk7-omap1 #97 Wed Sep 21 15:59:38 CEST 2005 armv4l
unknown
# /lib/libc.so.6
GNU C Library stable release version 2.2.5, by Roland McGrath et al.
Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 2.95.3 20010315 (release).
Compiled on a Linux 2.4.19 system on 2003-10-30.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.9 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Regards,
Frank
next prev parent reply other threads:[~2005-11-03 8:33 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 [this message]
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
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=20051103093306.qyr5bz57icqo04ck@admin.betaversion.net \
--to=frank@betaversion.net \
--cc=drow@false.org \
--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