[Octave-bug-tracker] [bug #65767] Inconsistent behavior of %!error and mexErrMsgIdAndTxt on different architectures

[Rafael Laboissière]

Follow-up Comment #5, bug #65767 (group octave):

Using of -fexceptions makes the problem go away, indeed. On the armhf system:


(sid_armhf-dchroot)rafael@abel:~/bug-1069477$ mkoctfile --mex --output
__buggy.mex buggy.c
(sid_armhf-dchroot)rafael@abel:~/bug-1069477$ echo test buggy | octave-cli
terminate called after throwing an instance of 'octave::execution_exception'
  what():  __buggy: Failed
fatal: caught signal Aborted -- stopping myself...
Aborted
(sid_armhf-dchroot)rafael@abel:~/bug-1069477$ CFLAGS="$(mkoctfile -p CFLAGS)
-fexceptions" mkoctfile --mex --output __buggy.mex buggy.c
(sid_armhf-dchroot)rafael@abel:~/bug-1069477$ echo test buggy | octave-cli
PASSES 1 out of 1 test




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65767>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/