This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/299: Single step/breakpoint problem
- From: andrej at funcom dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 29 Jan 2002 16:33:19 -0000
- Subject: gdb/299: Single step/breakpoint problem
- Reply-to: andrej at funcom dot com
>Number: 299
>Category: gdb
>Synopsis: Single step/breakpoint problem
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jan 29 08:38:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: andrej@funcom.com
>Release: CVS 2002-01-29 (and earlier dates)
>Organization:
>Environment:
Red Hat Linux v7.2 on a Dual Pentium III machine,
GCC: gcc version 3.0.2 20010905 (Red Hat Linux 7.1 3.0.1-3)
>Description:
When single-stepping the debugged program, GDB sometimes
does something similar to continue rather than stopping
on the next line/statement. When a breakpoint is then
hit, the program receives SIGSEGV, on the same line
as the breakpoint was set.
The debugged program is a fairly large multi-threaded
application (pthreads) written in C++, using several
shared libraries.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: