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++/1267: stepping does not work in shared libraries


>Number:         1267
>Category:       c++
>Synopsis:       stepping does not work in shared libraries
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 01 17:08:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     ldm@engr.uconn.edu
>Release:        GNU gdb 5.3.90_2003-06-29-cvs-debian
>Organization:
>Environment:
aegir /home/ldm/willow/proposals/CAREER [131] -> uname -a
Linux aegir 2.4.20 #17 SMP Thu May 1 17:10:22 EDT 2003 i686 GNU/Linux
Debian/sid
>Description:
I cannot use the next command when my code is compiled with shared libraries. Usually, I place a breakpoint in main, run the program, then set a breakpoint somewhere in one of my shared library and continue. 

When the program stops at the breakpoint the only commands that work reliably are
1) set breakpoint
2) step inside (step)

The step over (next) command has the same effect as continue. This makes the debugger almost unusable at I have to create tons of temporary breakpoints.

This has been going on for a while now (probably several months). 

>How-To-Repeat:
A C++ program. A C++ shared library (no dynamic loading necessary). Follow the step above after that. 
>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]