Thread: Strange behaviours

Sounds more like the code is crashing because of some other reason, not the DLL at all.

How do you catch it? <sarcasm mode> Have you tried using a debugger at all?</sarcasm mode>

Single-step the program with NO compiler optimisations and see what happens. Chances are you will discover that it crashes somewhere else entirely.

Also, if you want a "quick and dirty" test, just splat the function with printf's and other code in between calling the DLL and returning and outside the function from it's original call-point (which is where I'd focus my debug efforts, to be honest - sounds like you return a value that causes whatever code that called "cargarDLL" to crash). See what return values you are getting, what you're returning, what you're passing off to the DLL, etc. Call the function outside of everything else in your code (i.e. as close to being the first line of main() as you can get) with valid values and see what it does.

At a complete guess, I'd say you're returning something like a memory handle to local memory, or the code calling cargarDLL just isn't setup to handle whatever it returns

But you would be saved from a lot of my and your own guesses by just using a debugger. That's what they are there for. Hell, they're even pretty good at telling you if something crashes in a DLL you loaded, or even things like the C runtime and not your code.