Dear developers, While updating some Linuxbuilds today I received segmentation faults, when running the test suite. In this case I could turn on the debugger and generate the fault again.
Can you conclude anything from this message? Can I issue any command that you want to have run in gdb? I have no knowledge of the debugger so you will need to provide me the commands in that case. The version built is a release version of Linux Mint from today 11985, not a debug version Hälsningar/Regards/Grüsse, P.O. Jonsson [email protected] > Anfang der weitergeleiteten Nachricht: > > Von: LinuxMint Linux <[email protected]> > Betreff: Segmentation fault > Datum: 2. März 2020 um 17:15:51 MEZ > An: [email protected] > > > > + rexx -e 'parse version v; say v '\''r'\'' || .RexxInfo~revision' > REXX-ooRexx_5.0.0(MT)_64-bit 6.05 2 Mar 2020 r11985 > + sleep 1 > + ulimit -c 1000000 > + gdb -silent -ex=r --args rexx testOORexx.rex -s -X native_API > Reading symbols from rexx...(no debugging symbols found)...done. > Starting program: /usr/bin/rexx testOORexx.rex -s -X native_API > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > Searching for test containers[New Thread 0x7ffff7f55700 (LWP 405)] > [New Thread 0x7ffff7ed4700 (LWP 406)] > > Thread 1 "rexx" received signal SIGSEGV, Segmentation fault. > 0x00007ffff7af9671 in MemoryObject::markObjectsMain(RexxInternalObject*) () > from > /home/osboxes/workspace/ooRexx-mint19-build/oorexxBuild/lib/librexx.so.5.0.0 > (gdb) >
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
