This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: server/1242: can't single step in thread, get SIGTRAP
- From: "Glenn Miles" <glennrmiles at hotmail dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 21 Jan 2004 19:28:01 -0000
- Subject: Re: server/1242: can't single step in thread, get SIGTRAP
- Reply-to: "Glenn Miles" <glennrmiles at hotmail dot com>
The following reply was made to PR server/1242; it has been noted by GNATS.
From: "Glenn Miles" <glennrmiles@hotmail.com>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: server/1242: can't single step in thread, get SIGTRAP
Date: Wed, 21 Jan 2004 13:21:19 -0600
I'm seeing this same behavior with gdbserver (5.3) running on PPC as well
(with x86 client). Native gdb 5.3 on PPC is able to step without any
problems.
A workaround I've been using is to set the scheduler-locking mode to "step".
_________________________________________________________________
Find high-speed ?net deals ? comparison-shop your local providers here.
https://broadband.msn.com