Quote from: ckolivas on October 20, 2012, 09:34:10 PM

Quote from: P_Shep on October 20, 2012, 08:03:36 PM

Quote from: ckolivas on October 20, 2012, 12:21:08 PM

Even better would be a custom debug build running in gdb but I doubt any of you are up for that Undecided

I'm trying that on my laptop which is the only thing that has windows. Hopefully I don't fry it in the process, but at 10MH/s I also doubt it will recreate the problem.

Sigh. I wish it were only linux...

How do you do that? I tried something a while back but didn't get it working.

What I want to do is run under gdb, save the environment when it crashes, then continue running so that it's not sitting all day locked up.

When you build it, build it without optimisations in the CFLAGS and with the -g option, i.e. CFLAGS="-g -Wall -W" only. Then
gdb cgminer
run [usual cgminer parameters] -T
Running it with -T is a good idea cause gdb spews out other information and corrupts the display when you're using the curses display.

Here's a debug build in case someone is willing to try it:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Meanwhile my laptop continues to fry itself but has not crashed with the windows binary. It's probably too slow to even reproduce the problem.