From: Daniel Jacobowitz <drow@mvista.com>
To: Gerhard Tonn <TON@de.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: thread support doesn't work any more on s390
Date: Mon, 01 Jul 2002 07:51:00 -0000 [thread overview]
Message-ID: <20020701145039.GA1933@nevyn.them.org> (raw)
In-Reply-To: <OF209CB18A.940E854D-ONC1256BE9.004F97BB@de.ibm.com>
On Mon, Jul 01, 2002 at 04:40:14PM +0200, Gerhard Tonn wrote:
> Hi,
> the gdb thread support doesn't work any more since gdb 5.1 on s390. I get
> an
What version of GDB did you check with - 5.1, or CVS trunk? If not the
trunk, please try it; I think S/390 was originally missed because its
makefile fragments do not have "linux" in their names.
>
> Starting program: /home/ton/Threads/threadtest
> [New Thread 1024 (LWP 28211)]
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 1024 (LWP 28211)]
>
> when starting my threaded program.
>
> I have found in the NEWS file a section for 5.1
>
> >* Changes in GNU/Linux native debugging.
>
> >Support for debugging multi-threaded programs has been completely
> >revised for all platforms except m68k and sparc. You can now debug as
> >many threads as your system allows you to have.
>
>
> Could someone elaborate on what platform specific code has to changed,
> since I guess that this has to be done for s390 as well.
>
>
> Regards / Mit freundlichen Gruessen
> Gerhard
>
> Gerhard Tonn, Linux for eServer Development, +(49)-7031-16-4716, Lotus
> Notes: ton@ibmde,
> Internet: ton@de.ibm.com
>
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-01 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 7:45 Gerhard Tonn
2002-07-01 7:51 ` Daniel Jacobowitz [this message]
2002-07-02 1:09 Gerhard Tonn
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=20020701145039.GA1933@nevyn.them.org \
--to=drow@mvista.com \
--cc=TON@de.ibm.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).