It can help to enable core dumps, which can be used to debug after the program faulted. On Linux, use the following command to enable them for the current shell:
ulimit -c 1000000 Later use gdb to read them: gdb rexx core Moritz On Wed, Feb 20, 2019 at 3:30 PM P.O. Jonsson <oor...@jonases.se> wrote: > > Thanks for the info, will build with debug and try to install the debugger > then. Hopefully next time I have more info. > > For what it is worth here the last lines in /var/log/kern.log (seems to point > to librexx.so): > > Feb 19 19:58:35 ubuntu18-04 kernel: [ 5.735603] audit: type=1400 > audit(1550602715.004:11): apparmor="STATUS" operation="profile_load" > profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=587 > comm="apparmor_parser" > Feb 19 19:58:36 ubuntu18-04 kernel: [ 6.932503] IPv6: ADDRCONF(NETDEV_UP): > enp0s3: link is not ready > Feb 19 19:58:36 ubuntu18-04 kernel: [ 6.936425] IPv6: ADDRCONF(NETDEV_UP): > enp0s3: link is not ready > Feb 19 19:58:36 ubuntu18-04 kernel: [ 6.944100] e1000: enp0s3 NIC Link is > Up 1000 Mbps Full Duplex, Flow Control: RX > Feb 19 19:58:36 ubuntu18-04 kernel: [ 6.944427] IPv6: > ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready > Feb 19 19:59:00 ubuntu18-04 kernel: [ 31.532494] rfkill: input handler > disabled > Feb 20 11:11:36 ubuntu18-04 kernel: [54782.226713] show_signal_msg: 28 > callbacks suppressed > Feb 20 11:11:36 ubuntu18-04 kernel: [54782.226717] rexx[10888]: segfault at > 18 ip 00007ffa4466fff1 sp 00007ffdf0fb72f0 error 4 in > librexx.so.5.0.0[7ffa44502000+219000] > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > > Am 20.02.2019 um 15:08 schrieb Moritz Hoffmann <antig...@gmail.com>: > > This is good to know but unfortunately not helpful. See > https://sourceforge.net/p/oorexx/wiki/how-to-debug-oorexx/ on how to > get more useful information. > > Cheers, > Moritz > > On Wed, Feb 20, 2019 at 2:59 PM P.O. Jonsson <oor...@jonases.se> wrote: > > > Dear developers, > > I am building & testing on a number of different platforms and sometimes on > macOS/Darwin I get this when I come to the test (it all runs from a shell > script): > > REXX-ooRexx_5.0.0(MT)_64-bit 6.05 13 Feb 2019 r11755 > Searching for test containers./Users/po/workspace/testooRexx.sh: line 37: > 4122 Segmentation fault: 11 rexx testOORexx.rex -s -X native_API > > Today I had the same on Ubuntu for the first time: > > Searching for test containers... > /home/osboxes/workspace/testooRexx.sh: line 33: 10888 Segmentation fault > (core dumped) rexx testOORexx.rex -s -X native_API > osboxes@ubuntu18-04:~/workspace$ ^C > osboxes@ubuntu18-04:~/workspace$ > > There was a crash report on the Ubuntu desktop indicating usr/bin/rexx to be > the culprit but apart from that I could get no further information out. > Trying again a 2nd time it always work. > > Is there a way (on macOS or Ubuntu or any other system) to find out more > about this? I build „release“ version on all systems. Is such information at > all useful for U? > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > -- > Moritz Hoffmann; > http://antiguru.de/ > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Moritz Hoffmann; http://antiguru.de/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
