[Interest] Qt Creator Application Output window

[John Weeks]

Using Qt Creator 4.11.1 on Mac OS 10.14.6 with an Address Sanitizer build of our application.

As y'all may know, if you hit a problem in an Address Sanitizer build, the output from AS can be quite extensive. But very useful! Unfortunately, in the environment summarized above, the Application Output view in Qt Creator often fails to flush the output to the display, making it impossible to get all that useful information. See sample output copied from a recent run below. Looks like a buffering issue?

1) Is there a work-around? Some way to force the output to flush to the display?

2) Do others see this too?


-John Weeks

 =================================================================
==2501==ERROR: AddressSanitizer: heap-use-after-free on address 0x60300112fe40 at pc 0x0001052ca5ac bp 0x7ffeefbfa430 sp 0x7ffeefbfa428
READ of size 8 at 0x60300112fe40 thread T0
2020-04-22 09:14:45.998305-0700 atos[2944:31382] examining /Users/USER/Documents/*/Igor64.app/Contents/MacOS/Igor64 [2501]
2020-04-22 09:14:46.168427-0700 atos[2945:31394] examining /Users/USER/Documents/*/Igor64.app/Contents/MacOS/Igor64 [2501]
    #0 0x1052ca5ab in GetRawWaveUnits(waveHdr**, int, char*, int) WaveUnits.cpp:203
    #1 0x1052ca7d8 in GetWaveUnits(waveHdr**, int, char*, int) WaveUnits.cpp:263
    #2 0x104538c2e in GetUnits(std::__1::shared_ptr<axisRec>, char*) axislabel.cpp:116
    #3 0x1044ad071 in IsDateAxis(std::__1::shared_ptr<axisRec>) axis.cpp:6000
    #4 0x104c0d95b in SetAxisInfo(grafRec*, std::__1::shared_ptr<axisRec>, int) plotdata.cpp:2559
    #5 0x104c173a2 in UpdateGrafAxes(grafRec*, int) plotdata.cpp:2979
    #6 0x104c1f714 in UpdateGraf(grafRec*) plotdata.cpp:3459
    #7 0x104c2342c in DoUpdtDisplay(int) plotdata.cpp:3706
    #8 0x104c22cb7 in UpdtDisplay(int) plotdata.cpp:3761
    #9 0x1002190e1 in IgorAppObject::doIdleEvent(bool) IgorAppObject.cpp:4222
    #10 0x100217a98 in IgorAppObject::timerEvent(QTimerEvent*) IgorAppObject.cpp:3704
    #11 0x117dec5e5 in QObject::event(QEvent*) qobject.cpp:1228
    #12 0x11752211a in QGuiApplication::event(QEvent*) (QtGui:x86_64+0x3011a)
    #13 0x116d08802 in QApplication::event(QEvent*) qapplication.cpp:2022
    #14 0x100217474 in IgorAppObject::event(QEvent*) IgorAppObject.cpp:3697
    #15 0x116d09fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) qapplication.cpp:3722
    #16 0x116d0b347 in QApplication::notify(QObject*, QEvent*) qapplication.cpp
    #17 0x1001ff3ca in IgorAppObject::notify(QObject*, QEvent*) IgorAppObject.cpp:914
    #18 0x117dc3563 in QCoreApplication::notifyInternal2(QObject*, QEvent*) qcoreapplication.cpp:1024
    #19 0x117e19313 in QTimerInfoList::activateTimers() qcoreapplication.h:233
    #20 0x11f0fe261 in QCocoaEventDispatcherPrivate::activateTimersSourceCallback(void*) qcocoaeventdispatcher.mm:124
    #21 0x7fff460bce32 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (CoreFoundation:x86_64h+0x57e32)
    #22 0x7fff460bcdd8 in __CFRunLoopDoSource0 (CoreFoundation:x86_64h+0x57dd8)
    #23 0x7fff460a079a in __CFRunLoopDoSources0 (CoreFoundation:x86_64h+0x3b79a)
    #24 0x7fff4609fd64 in __CFRunLoopRun (CoreFoundation:x86_64h+0x3ad64)
    #25 0x7fff4609f66d in CFRunLoopRunSpecific (CoreFoundation:x86_64h+0x3a66d)
    #26 0x7fff452fe1aa in RunCurrentEventLoopInMode (HIToolbox:x86_64+0xb1aa)
    #27 0x7fff452fdee4 in ReceiveNextEventCommon (HIToolbox:x86_64+0xaee4)
    #28 0x7fff452fdc75 in _BlockUntilNextEventMatchingListInModeWithFilter (HIToolbox:x86_64+0xac75)
    #29 0x7fff4369577c in _DPSNextEvent (AppKit:x86_64+0x1a77c)
    #30 0x7fff4369446a in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] (AppKit:x86_64+0x1946a)
    #31 0x7fff