Bug 9248 - gdb reports Program exited normally when it should not
Summary: gdb reports Program exited normally when it should not
Status: RESOLVED OBSOLETE
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: 6.3
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-04 07:18 UTC by matty_gardiner
Modified: 2014-09-12 22:56 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matty_gardiner 2006-07-04 07:18:01 UTC
[Converted from Gnats 2143]

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

Release:
gdb-6.3

Environment:
Distro
------
Fedora Core 3

uname -a
--------
Linux <hostname> 2.6.12.2 #5 SMP  <datetime> i686 i686 i386 GNU/Linux

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.
Comment 1 Sergio Durigan Junior 2011-11-09 20:09:43 UTC
Some reproducer would certainly help here.
Comment 2 Sergio Durigan Junior 2014-09-12 22:56:57 UTC
Closing as OBSOLETE due to inactivity.  Feel free to reopen if still valid.