epicsAssert() message lost

Bug #1424092 reported by mdavidsaver
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Triaged
Low
mdavidsaver

Bug Description

I am seeing that epicsAssert() messages are losing the first few lines, including the assertion message. I suspect this is a bug with errlogFlush(), which is called epicsStackTrace() after the assertion message is printed, but before the stacktrace is printed.

This is with present lp:epics-base

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

The attached shows the complete output unittest which triggers an assertion failure with the first lines missing.

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

The assertion being triggered in this example is

> assert(realcount>0);

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

This is still on my todo list.

Changed in epics-base:
assignee: nobody → mdavidsaver (mdavidsaver)
importance: Undecided → Low
status: New → In Progress
Changed in epics-base:
status: In Progress → Triaged
Revision history for this message
mdavidsaver (mdavidsaver) wrote :

May be resolved by b9899213d4e61de8cc28e0006bf5196e605f676e cf. https://github.com/epics-base/epics-base/pull/113

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.