I'm getting issues loading an object but MMF2 is supplying no information.
Attachment 6819
I'd like b256 to contain useful error messages.
In the meantime a paid project I'm working on had to have the object removed in order for development to continue...
The build version of the object vs the MMF2 version are correct.
Uninformative attachment.
That's the entirety of the error log, Yves...
Attachment 6805
Like my Windows XP theme?
MMF2 cannot load extensions for 2 reasons :
1. They depend on DLLs that are not on the machine.
2. Or if they crash in the DllMain or Initialize functions and the exception is intercepted by MMF2.
Probably I could display a different message in the second case "This extension crashes when MMF2 tries to load it", but usually it's quite easy to find out if that's reason one or two.
You could go a step further Yves, and explain the exception code
Is that really the only information you can obtain is that the failure happened?
With regards to crashing, EDIF's Initialize() is fine but their Free() has been giving issues for me, trying to delete something it shouldn't.
Is 3. They have a higher build number?
Higher build numbers shouldn't crash. They just won't function or appear in the list
True, but no one said that my one was crashing
Yves, I'd like it if you could make catching-crashes optional, I find it difficult to debug what's crashing when MMF insta-closes. It's very irritating to be testing an object and have MMF2 just close without warning.
Also, have you read my blog post about debug symbols? I'm wanting private debug symbols for MMf2 more and more as I work on the DarkEDIF SDK.
I already catch crashes when MMF2 starts, of course. Do you use an extension created with the old Edif SDK? The old Edif SDK corrupts the stack of the the Unicode version of MMF2 and in this case cacthing the exceptions doesn't work, very boring, that's why I had to add the "Extensions to ignore" tab in the latest build. Use the latest version of Edif to develop your extensions. Otherwise check if your extension could corrupt the stack and prevent MMF2 from catching the catch exception.Yves, I'd like it if you could make catching-crashes optional, I find it difficult to debug what's crashing when MMF insta-closes. It's very irritating to be testing an object and have MMF2 just close without warning.
I saw your post about the debug symbols, but there are many program files, not sure if I'll time to release that some day.
No, I'm actually creating a new update/derivative of EDIF called DarkEDIF, and it's experimental, hence the desire to catch the crashes first-hand
With regards to the debug symbols, the private symbols for MMF2.exe & edrt.exe should mostly cover it for using the object in one of the MMF2 editors, and for edittime debugging, respectively. It's as simple as changing two options in the project configuration. That's about 8 sets of changes, including Dev and Unicode of both apps.
Posting Permissions
Reply With Quote