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: Daniel Jacobowitz <drow at mvista dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 22 Jan 2004 20:58:01 -0000
- Subject: Re: server/1242: can't single step in thread, get SIGTRAP
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR server/1242; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: Glenn Miles <glennrmiles@hotmail.com>, gdb-gnats@sources.redhat.com
Cc:
Subject: Re: server/1242: can't single step in thread, get SIGTRAP
Date: Thu, 22 Jan 2004 15:54:40 -0500
On Wed, Jan 21, 2004 at 07:28:01PM -0000, Glenn Miles wrote:
> 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".
Could you try GDB 6.0, please? I believe this is fixed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer