Closed matteofranceschini closed 8 months ago
The compiler says: "large integer implicitly truncated to unsigned type". Try defining CEXCEPTION_NONE as a 16-bit unsigned integer, for example 0x5A5A.
@matteofranceschini -- I'm wondering if @deltalejo 's advice solved your problem? I realize this was a long time ago and you've likely moved on to other solutions if you were not able to get this to work... but I'd appreciate knowing if we have a problem that needs to be investigated here.
Hey! I actually gave it a try, but it didn't work out of the box. I'll probably make some tests in the near future: I'm planning to get back on this project in the next month or so :)
I'll give more feedback about it! :)
I had a similar error "Expected 0x5A5A5A5A Was 0x00000000. Unhandled Exception!"
and was able to solve it by putting the following in a support file.
#define CEXCEPTION_NONE (0x00000000)
So I imagine if you did the same, but defined it to 0x00008B97
that it would solve it.
Hi! I'm trying to use your library on some test project to learn something new, but with a simple "main" that only does this:
with SYSTEM_Initialize() that has
it continuously goes into the catch, with or without "e" initialized and with or without the throw commented out (that shouldn't be called, anyway).
I tried also to debug it from MPLABX v5.35, XC16 V1.50 and after i get out from System_Initialize() i still have
e=CEXCEPTION_NONE
, when initialized, ore=0xFFFF
when not initialized but I don't understand why it goes into the catch anyway.I then tried to run your test (the one included with your library), and luckily it fails in the same way (at least, I have some correlation):
The first test does exactly what my main does, therefore I expected this behavior. For reference, I'm using ceedling (locally initialized with its libraries, CException included) with this project yaml:
and calling the MDB simulator with this code:
That calls these commands:
Any help is appreciated, I'd love to use your libraries in my projects :)
EDIT: I initially had "use exceptions: FALSE" with the manually added path for tests pointing to the "vendor" folder (see edit history). By changing "use exceptions" true and erasing the path to "vendor" the test worsened the result: