This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: breakpoints/1894: SIGTRAP after stepping and calling a function twice
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 8 Mar 2005 20:08:00 -0000
- Subject: Re: breakpoints/1894: SIGTRAP after stepping and calling a function twice
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR breakpoints/1894; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: fc@oasys-design.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: breakpoints/1894: SIGTRAP after stepping and calling a function twice
Date: Tue, 8 Mar 2005 15:07:36 -0500
On Tue, Mar 08, 2005 at 07:39:59PM -0000, fc@oasys-design.com wrote:
>
> >Number: 1894
> >Category: breakpoints
> >Synopsis: SIGTRAP after stepping and calling a function twice
> >Confidential: no
> >Severity: serious
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Tue Mar 08 19:48:01 UTC 2005
> >Closed-Date:
> >Last-Modified:
> >Originator: fc@oasys-design.com
> >Release: 6.3
> >Organization:
> >Environment:
> Linux (Fedora Core 1-3)
> >Description:
> Anytime a second function is being called after a 'next' step, you get "Program received signal SIGTRAP, Trace/breakpoint trap."
>
> I have a very simple testcase. Running the foll commands "break main; run; next; call foo(); call bar()" will cause the SIGTRAP. Note the 'next', as well as 2 calls, is needed to trigger this problem.
>
> This fails in 6.3.0 and 6.3.50. It is ok in 5.3.90.
> >How-To-Repeat:
> compile bug.cc, and debug with "break main; run; next; call foo(); call bar()"
I can't reproduce this. It looks very much like a Linux kernel bug
which I fixed last week; you may want to try a different kernel
version.
--
Daniel Jacobowitz
CodeSourcery, LLC