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 404631 - [check] print stack trace on segfault in unit tests
[check] print stack trace on segfault in unit tests
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal enhancement
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-05 15:47 UTC by Tim-Philipp Müller
Modified: 2015-03-17 15:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch, prints a stack trace when a unit test crashes (if supported) (2.89 KB, patch)
2007-02-05 15:48 UTC, Tim-Philipp Müller 		none Details | Review
Re-base of patch to gst-1.5 (3.84 KB, patch)
2015-03-17 15:04 UTC, A Ashley 		none Details | Review

Description Tim-Philipp Müller 2007-02-05 15:47:17 UTC 
Today there was a spurious unit test crash on one of the build bots, which turned out not to be reproducable.

It would be nice if in cases like that we could print a stack trace automatically, so the build bot log gives us at least a hint as to what might have caused the crash.

Attaching proposed patch. Works fine for me.
Comment 1 Tim-Philipp Müller 2007-02-05 15:48:15 UTC 
Created attachment 81937 [details] [review]
patch, prints a stack trace when a unit test crashes (if supported)
Comment 2 Tim-Philipp Müller 2007-05-18 19:57:14 UTC 
Obviously no interest, closing (also it doesn't print the very last frame, so it's not quite as useful as it looks).
Comment 3 A Ashley 2015-03-17 15:04:07 UTC 
Created attachment 299605 [details] [review]
Re-base of patch to gst-1.5

Rebase of the patch to gstreamer 1.5. Ignore the gst-indent cruft at the end of the patch. Wasn't worth fighting git for a "won't fix" ticket.

Shame there wasn't much interest in the patch, it's certainly helping me try to find why my check is seg-faulting!
Comment 4 Tim-Philipp Müller 2015-03-17 15:17:52 UTC 
It might be worth reconsidering this patch, it might be useful when run on build bots (once the buildbots actually show the info output by the tests and not just the failure).

If you're trying to debug a crash in a unit test, you'd typically do:

  tests/check $ make foo/bar.gdb

or

  tests/check $ make foo/bar.valgrind