[QUOTE=flashjh;304034]When you build, what do you use to include debugging info? I use MSVS command line, so the /DEBUG doesn't work.

I've been trying to move the projects to the full MSVS, but I haven't spent a lot of time getting it to work yet.[/QUOTE]

I usually do
[code]
... /DEBUG /PDB "outfile.pdb" ...
[/code]

This way you have a small exe file you can send around, and if you need the debug info, just send the matching pdb along ... Hmm, I notice, I did not do that for mfakto yet ...

[QUOTE=Bdot;304037]I usually do
[code]
... /DEBUG /PDB "outfile.pdb" ...
[/code][/QUOTE]

Do you use /DEBUG with the linker or cl? For me, when I use /DEBUG with cl, it won't even compile.

I just used /DEBUG with the linker and it made the .pdb file, they are uploaded to the [URL="https://sourceforge.net/projects/cudalucas/files/2.04%20Beta/?"]2.04 beta folder[/URL].

Real quick, are all these new versions with Bdot's unmodified code?

And is not /DEBUG merely defining "EBUG" for the preprocessor, not actually including debugging symbols? I will say that most of your conversation is gibberish to me. :smile:

PS Even if Bdot's original code also doesn't work, I still suspect it's a MSFT library/API function problem, because his Linux code is working fine for me.

[QUOTE=Dubslow;304052]Real quick, are all these new versions with Bdot's unmodified code?

And is not /DEBUG merely defining "EBUG" for the preprocessor, not actually including debugging symbols? I will say that most of your conversation is gibberish to me. :smile:[/QUOTE]

:wink:
these are options to the linker, otherwise ... you're right.

Is that the reason for the new lines like these in filelocking.c?
[code]
#ifdef EBUG
...
[/code]

I'll test the debug symbols tomorrow.

Whenever I need to conditionally insert print statements, I use EBUG, because then I can do '-DEBUG'. :smile:

In this case, that's leftover from when I initially added the file lock code; I added those print statements just to convince myself I was actually calling the right functions at the right time. I didn't actually do any debugging, because everything appeared to be working.

[QUOTE=Dubslow;304057]PS Even if Bdot's original code also doesn't work, I still suspect it's a MSFT library/API function problem, because his Linux code is working fine for me.[/QUOTE]
Ok, I got home today and CL finally produced the same error. Strange thing is I've done 2 other exponents with no problems. I'll do some troubleshooting to see what I can find. The debugging isn't working for MSVS because it's compiled with the command prompt. Tomorrow I'm going to see if I can get CL to compile in MSVS. If anyone can use the debgging info included in the debug version, let me know.

[QUOTE=Bdot;304013] A stacktrace would certainly be of great help. If you can get the debug symbols for your build, then you can even look at the data / variables ...[/QUOTE]

Stack trace wasn't helpful at all and I have no debug info :-(

[QUOTE=flashjh;304029]I [URL="https://sourceforge.net/projects/cudalucas/files/2.04%20Beta/"]uploaded[/URL] a 3.2 x64 version with dubug info (hopefully). If someone could test the debug and let me know, I would appreciate it.[/QUOTE]

That one didn't crash.

And I lost my saved checkpoints so it will take a little bit until I get another set.

[QUOTE=flashjh;304064]Ok, I got home today and CL finally produced the same error. Strange thing is I've done 2 other exponents with no problems. I'll do some troubleshooting to see what I can find. The debugging isn't working for MSVS because it's compiled with the command prompt. Tomorrow I'm going to see if I can get CL to compile in MSVS. If anyone can use the debgging info included in the debug version, let me know.[/QUOTE]

I've compiled the version I got from SF in GUI MSVS but that one behaves with smallest exponent. Didn't have a chance to test with the other ones. Also I'm not sure which version is used to compile the crashing executable...

[QUOTE=apsen;304077]I've compiled the version I got from SF in GUI MSVS but that one behaves with smallest exponent. Didn't have a chance to test with the other ones. Also I'm not sure which version is used to compile the crashing executable...[/QUOTE]

What settings do you use in MSVS?

The debug version is the latest revision.