This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

c++/1803: stepping into function causes segmentation violation

From: achin at axsone dot com
To: gdb-gnats at sources dot redhat dot com
Date: 2 Nov 2004 22:13:54 -0000
Subject: c++/1803: stepping into function causes segmentation violation
Reply-to: achin at axsone dot com

>Number:         1803
>Category:       c++
>Synopsis:       stepping into function causes segmentation violation
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 02 22:18:02 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Al Chin
>Release:        6.2.1
>Organization:
>Environment:
SunOS 5.8 Generic_108528-27 sun4u sparc SUNW,Ultra-Enterprise, g++ (GCC) 3.3.2, GNU gdb 6.2.1, ddd 2.8.1
>Description:
Program received signal SIGSEGV, Segmentation fault when trying to step into another function.  There are many shared libraries loaded.  If I set a breakpoint inside the function and then continue, it stops fine.  If I don't use gdb the program runs fine or at least past the function in question.
>How-To-Repeat:
Unsure of what the exact set of circumstances are.  Other (statically linked) programs debug fine.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]