On 03/28/2018 12:56 PM, John Reiser wrote: >> I've just discovered that gdl appears to be segfaulting a lot now deep in >> the antlr c++ generated parser code with the switch to gcc 8. > > A bugzilla report would be nice. Run under gdb, report register contents > and the instruction stream surrounding $pc, etc. Also any clues > about the corresponding location in the source code. > > Is the SIGSEGV deterministic (reproducible every time) or random? > Does memcheck (valgrind --track-origins=yes) complain? It's entirely reproducible. I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1566242 with what I can glean. I don't understand the backtrace though. Seems like a destructor is getting called when initializing a class variable. Very strange to me, but I'm no C++ expert. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 https://www.nwra.com/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
