This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1657: When gdb pass SIGTRAP to application, signal info has been changed by gdb
- From: daihb at ffcs dot fujitsu dot co dot jp
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 May 2004 03:38:06 -0000
- Subject: gdb/1657: When gdb pass SIGTRAP to application, signal info has been changed by gdb
- Reply-to: daihb at ffcs dot fujitsu dot co dot jp
>Number: 1657
>Category: gdb
>Synopsis: When gdb pass SIGTRAP to application, signal info has been changed by gdb
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 25 03:48:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: daihb
>Release: 6.1
>Organization:
>Environment:
Solaris 8.0
gcc 3.3
gdb 6.1
>Description:
My application has used virtual memory watchpoints mechanism (refer to [solaris internal] section 5.6). When accessing memory address which has been registered as watchpoint, a SIGTRAP signal will be generated with accessed address in signal info. I have test this application under dbx. It is no problem. But when I test this application under gdb, some error occur. The signal info has been changed by gdb when gdb pass SIGTRAP to application. Maybe it is a bug of gdb.
Any input is greatly appreciated.
Thanks.
daihb
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: