CUDALucas (a.k.a. MaclucasFFTW/CUDA 2.3/CUFFTW) - Page 135

Bdot · 2012-07-04, 16:09

Quote:

Originally Posted by flashjh

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.

I usually do

Code:

... /DEBUG /PDB "outfile.pdb" ...

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 ...

flashjh · 2012-07-04, 16:32

Quote:

Originally Posted by Bdot

I usually do

Code:

... /DEBUG /PDB "outfile.pdb" ...

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 2.04 beta folder.

Dubslow · 2012-07-04, 18:33

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.

Dubslow · 2012-07-04, 19:49

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.

Bdot · 2012-07-04, 19:54

Quote:

Originally Posted by Dubslow

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.

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
...

I'll test the debug symbols tomorrow.

Dubslow · 2012-07-04, 21:36

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

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.

flashjh · 2012-07-05, 03:44

Quote:

Originally Posted by Dubslow

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.

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.

apsen · 2012-07-05, 12:47

Quote:

Originally Posted by Bdot

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 ...

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

apsen · 2012-07-05, 12:54

Quote:

Originally Posted by flashjh

I uploaded a 3.2 x64 version with dubug info (hopefully). If someone could test the debug and let me know, I would appreciate it.

That one didn't crash.

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

apsen · 2012-07-05, 13:02

Quote:

Originally Posted by flashjh

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.

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...

flashjh · 2012-07-05, 14:22

Quote:

Originally Posted by apsen

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...

What settings do you use in MSVS?

The debug version is the latest revision.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Don't DC/LL them with CudaLucas	LaurV	Data	131	2017-05-02 18:41
CUDALucas / cuFFT Performance on CUDA 7 / 7.5 / 8	Brain	GPU Computing	13	2016-02-19 15:53
CUDALucas: which binary to use?	Karl M Johnson	GPU Computing	15	2015-10-13 04:44
settings for cudaLucas	fairsky	GPU Computing	11	2013-11-03 02:08
Trying to run CUDALucas on Windows 8 CP	Rodrigo	GPU Computing	12	2012-03-07 23:20

2012-07-04, 18:33	#1477
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	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.

2012-07-04, 19:49	#1478
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 7221₁₀ Posts	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.

2012-07-04, 21:36	#1480
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	Whenever I need to conditionally insert print statements, I use EBUG, because then I can do '-DEBUG'. 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.