[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #36067] faulty mex/oct file with bad pointer a
From: |
Nicholas Jankowski |
Subject: |
[Octave-bug-tracker] [bug #36067] faulty mex/oct file with bad pointer assignments can crash Octave |
Date: |
Tue, 18 Apr 2023 13:11:34 -0400 (EDT) |
Follow-up Comment #20, bug #36067 (project octave):
it's been a few years, this could use a reminder from those familiar with the
issue what the remaining trigger case is.
using the attached test code, here's the current output i get. Can't trigger a
crash. But can trigger an error with which:
>> mkoctfile --mex causesegfault.cpp
>> exist('causesegfault.mex','file')
ans = 3
>> exist('causesegfault.mex')
ans = 3
>> exist('causesegfault')
ans = 3
>> which causesegfault
will crash now
error: opening the library 'C:\temp\octave\causesegfault.mex' failed (error
1114): A dynamic link library (DLL) initialization routine failed.
>> causesegfault
will crash now
error: opening the library
'C:\Users\nicholas.jankowski\Desktop\temp\octave\causesegfault.mex' failed
(error 1114): A dynamic link library (DLL) initialization routine failed.
so, even the intended segfault produces an error instead of crashing octave,
but in any case I can't trigger it with exist. is there a better test case to
use now?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?36067>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #36067] faulty mex/oct file with bad pointer assignments can crash Octave,
Nicholas Jankowski <=