After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731366 - run-assert-msg-test.sh gdb leaves assert-msg-test zombie
run-assert-msg-test.sh gdb leaves assert-msg-test zombie
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: build
2.38.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-06-08 02:25 UTC by Daniel Macks
Modified: 2014-06-10 12:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Explicitly quit gdb session to avoid zombie (810 bytes, patch)
2014-06-10 10:05 UTC, Daniel Macks
committed Details | Review

Description Daniel Macks 2014-06-08 02:25:21 UTC
I built glib-2.38.2 on OS X 10.8, and my "gdb" is /usr/bin/gdb as supplied by Apple as part of XCode-5.1.1. Running 'make check' in the tests subdir yields:

PASS: run-assert-msg-test.sh

However, 'ps' reveals a zombie assert-msg-test process. I have separate user account for build sandboxing, and simply running that .sh directly:

 sudo -u fink-bld ./run-assert-msg-test.sh

leaves one new zombie every time. Looks like the gdb session aborts before terminating the sublaunched process. Adding a "quit" to the end of assert-msg-test.gdb lets me run that sudo command repeatedly with no new zombies created.
Comment 1 Daniel Macks 2014-06-10 10:05:37 UTC
Created attachment 278195 [details] [review]
Explicitly quit gdb session to avoid zombie