This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
breakpoints/1894: SIGTRAP after stepping and calling a function twice
- From: fc at oasys-design dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 8 Mar 2005 19:39:59 -0000
- Subject: breakpoints/1894: SIGTRAP after stepping and calling a function twice
- Reply-to: fc at oasys-design dot com
>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()"
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-tar; name="bug.tar"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.tar"
H4sIAFn+LUIAA+3Vy06DQBQGYLadpzipG5uGcodEjWs3voGbAaZ0UjqYAaqJ+u4OLbaxSdsVbYz/
txkyc2C45OekbeGkbTHLMmswrhGH4WZM4t9jx3dDy3N9LwiSOAgjy/X82E8scoe7pb22brgmshZc
r07VnVvvn2U3/hE3UmVlmwt6qJtcVrPFI2PrSuY0r6rbCftgRK9aqmZ+OzYzL2o8uWdffUnK9UGJ
mdmVmBlacakOSp5EWVb0Vuky/ym99jv4z0z2nWe+FHNZiqH22OQ/Pp5/L+7z70dxEnX5D3wvRP4v
gZflHRsV0ynZBW0bAdlVd8RGC8Fzsj1yRJM5sq5bwUat4itBtjbndJX2WuhaVoo+qa82C3l6fKG7
8LWfGfa6/M/Mh5FKNkPtcS7/buTv+n8UuF3+vThA/i8h1YIvN32a6VYxJd4blpmfQt//N4fbPn/t
OwUAAAAAAAAAAAAAAAAAgFO+AeHOKmEAKAAA