EXCEPTION_ACCESS_VIOLATION
BlitzMax Forums/Brucey's Modules/EXCEPTION_ACCESS_VIOLATION
| ||
Anyone else getting this error with the new blitzmax 1.37? This happens in the cegui.mod directory. The error occurs just after the IDE prints the Compiling:CEGUIFalXMLEnumHelper.cpp Don't know if this helps, but that's all the IDE says. |
| ||
I got the exception_access_violation when trying to recompile the CEGUI module using the official bmk.exe -- it compiled without errors after replacing bmk.exe with Brucey's BMK NG. |
| ||
Getting the same thing here on Win7 blitzmax 1.37 with the standard BMK.. When I try the same with a BMK built with debug, I get 'Unhandeled Exception:Attempt to access field or method of Null object'. And the IDE pop the 'bmk.bmx' file, and highlight line number 110. Function MakeModules( args$[] ) If args.length>1 CmdError If args.length SetModfilter args[0] Else opt_modfilter="" Local mods:TList=EnumModules() BeginMake MakeMod "brl.blitz" For Local name$=EachIn mods MakeMod name <------ THIS ONE Next End Function |
| ||
Hmmm... I suppose I should dig out an original bmk and try to track it down.. |
| ||
And failing on OpenSuse 11.1 with a segmentation fault to. Didn't do a debug build of the BMK there, but guessing it's related.. EDIT: Ok, did a debug build, and fail with the same error as above. |
| ||
The error is in an attempt to process a file stack.hh It fails the ValidSourceExt() test, which causes the variable src_file in MakeSrc() to be Null. That results in "Else If src_file.framewk" falling over for obvious reasons. This is what the official bmk code looks like : Local src_file:TSourceFile=ParseSourceFile( src_path ) This is what my own bmk looks like : Local src_file:TSourceFile=ParseSourceFile( src_path ) If Not src_file Return Which is why mine doesn't crash in this case. I would raise it as a Bug for Mark to fix :-) |
| ||
Because my bmk likely gets a lot more workout than a typical installation (because of building, and rebuilding, and experimenting with new libraries), it's more likely to have hit these issues a long time ago. Sometimes I might assume that a crash is due to my self, and therefore won't consider that the original code may be flawed. |