This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2143: gdb reports Program exited normally when it should not
- From: matty_gardiner at yahoo dot co dot uk
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Jul 2006 07:16:42 -0000
- Subject: gdb/2143: gdb reports Program exited normally when it should not
- Reply-to: matty_gardiner at yahoo dot co dot uk
>Number: 2143
>Category: gdb
>Synopsis: gdb reports Program exited normally when it should not
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jul 04 07:18:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Matthew Gardiner
>Release: gdb-6.3
>Organization:
>Environment:
Distro
------
Fedora Core 3
uname -a
--------
Linux <hostname> 2.6.12.2 #5 SMP <datetime> i686 i686 i386 GNU/Linux
>Description:
The program occurs when I attempt to debug my SIP server. This is a multithreaded C++ program which uses pthreads and sockets.
when I run gdb <program>, as soon as a client program attaches gdb reports that "Program exited normally" and the debugged program stops running. (This does not happen when the program is being ran outside of gdb).
Do I need to build gdb in a particular way to support this (SMP?) hardware?
Is there something obvious I am doing wrong to cause gdb to continually report "Program exited normally"?
Any help gratefully received,
Matthew Gardiner
>How-To-Repeat:
I invoke "gdb sipserver"
Set args at (gdb) prompt
Run at (gdb)
"ps ax" now reports my server to be running.
Invoke a client program (standalone outside of debugger). Once the client attempts to connect a socket to the server the (gdb) prompt reports "Program exited normally" and it is no longer reported by ps.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: