Back to the main page.
Bug 2642 - invalid MEX-file???
| Status | CLOSED INVALID |
| Reported | 2014-07-09 10:46:00 +0200 |
| Modified | 2019-08-10 12:28:29 +0200 |
| Product: | FieldTrip |
| Component: | inverse |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P5 normal |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
- 2014-07-09 10:46:44 +0200
Hey guys, This is a recent error (since last night): ??? Invalid MEX-file '/home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64': /home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64: failed to map segment from shared object: Cannot allocate memory Error in ==> ft_read_event at 116 eventformat = ft_getopt(varargin, 'eventformat'); I also got: ??? Invalid MEX-file '/home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64': /home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64: failed to map segment from shared object: Cannot allocate memory Error in ==> ft_read_event at 116 eventformat = ft_getopt(varargin, 'eventformat'); ??? Invalid MEX-file '/home/common/matlab/fieldtrip/utilities/private/memprofile.mexa64': /home/common/matlab/fieldtrip/utilities/private/memprofile.mexa64: failed to map segment from shared object: Cannot allocate memory Error in ==> memtic at 86 memstat = memprofile('info'); Error in ==> ft_preamble_provenance at 113 ftohDiW7th_FuncMem = memtic(); Error in ==> ft_preamble at 54 evalin('caller', ['ft_preamble_' cmd]); Error in ==> ft_definetrial at 120 ft_preamble provenance Any ideas what's up? PS - This is on a mentat.
Robert Oostenveld - 2014-07-09 11:05:47 +0200
hi Tom, The mex file has not been changed recently. Also the one on home/common is exactly the same as an (not recently updated) one in my home directory: roboos@mentat001> md5sum /home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64 66fed38710d6c102be93161839d61264 /home/common/matlab/fieldtrip/fileio/private/ft_getopt.mexa64 roboos@mentat001> md5sum ./ft_getopt.mexa64 66fed38710d6c102be93161839d61264 ./ft_getopt.mexa64 I suspect it to be a hickup of the filer or of the mental. Is it still reproducible?
- 2014-07-09 12:16:09 +0200
Yes, as of 12.15 today.
- 2014-07-09 13:17:48 +0200
Bug no longer valid. Restarting on a new VNC solved the problem. Apologies. No idea what the problem was but it is fine now.