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]

gdb/1233: gdb causes 'abort' signal when debugging cvs


>Number:         1233
>Category:       gdb
>Synopsis:       gdb causes 'abort' signal when debugging cvs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 04 01:38:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     esp@pyroshells.com
>Release:        unknown-1.0
>Organization:
>Environment:
sun solaris 5.8, gcc-3.2.3, gdb-5.3
>Description:
when debugging cvs server, gdb causes a 'signal 5' (abort) after inserting a breakpoint in certain functions.

No abort signal occurs when there are no breakpoints.
>How-To-Repeat:
1) download and compile with debugging, cvs-1.11.5.
2) make a cvs tree on a server machine
3) set CVS_CLIENT_LOG on another machine (a client)
4) run a 'cvs update -d <directory>' on the client machine against a live cvs tree to generate a client log
5) run, under gdb, cvs on the server machine which mirrors the cvs log
6) put a breakpoint on the function 'update' inside the gdb session
7) run cvs with 'r server < the_cvs_client_log.in'
8) the breakpoint will occur inside the function update
9) continue
10) the code will abend with a signal #5

If you don't set a breakpoint, the code should continue, and you'll get lots of output to stdout.
>Fix:
my guess is that it has something to do with stepping into a function pointer, but I have no clue. its fairly annoying though.
>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]