assert fail message should include a stack trace?

Bug #541223 reported by Jeff Hill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Wishlist
Unassigned

Bug Description

It would be very useful if a stack trace was included in assert fail messages. This is easy on vxWorks, and may also be possible without unreasonable effort on Windows and Linux. On vxWorks we provide instructions to the user on how to obtain a stack trace, but this rarely results in a stack trace being sent with the bug report, so perhaps it would be best to just go ahead and dump a stack trace when the assert message is generated.

Original Mantis Bug: mantis-166
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=166

Related branches

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

Both epicsAssert() and cantProceed() now print a stack trace.

Changed in epics-base:
milestone: none → 3.16.branch
status: New → Fix Committed
Andrew Johnson (anj)
Changed in epics-base:
milestone: 3.16.branch → 3.15.branch
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.