different yafu folder specified in aliqueit.ini?
resume flags specified in the yafu ini?
delete the temp files and siqs.dat? (otherwise it just takes the settings already used for the job?)

[QUOTE=LaurV;383508]different yafu folder specified in aliqueit.ini?
resume flags specified in the yafu ini?
delete the temp files and siqs.dat? (otherwise it just takes the settings already used for the job?)[/QUOTE]

Ah, yes I forgot about the save file, thanks

New bug
 

Using v1.34.5 in Win 64 with an i7 x940 @2.13 GHz and 16 Gb RAM, I consistently get a crash with the following command

[code]
yafu "factor(1362451646784891369931269337270434227979248871480462196846331708138656372770855137598650006001648841269932786068139129328455191133597270664753316104049397774641209284405381228642878882897501005284365400690476297)" -v -noecm
[/code]

Yafu runs through the abbreviated factoring routine, starts to generate polys to consider, then crashes (always on the same poly).

I've used the factor() command to check for small factors and then move into snfs many times in the past with no problem.

This number is a composite cofactor of the xyyx number C211_128_95.

Thoughts? Can anyone else duplicate this bug?

Which polynomial did it fail on? I used your command and it generated a bunch of polynomials and is currently test-sieving them to choose the best one.

Edit: It completed fine for me and started into the actual sieving.

[QUOTE=wombatman;385250]

Edit: It completed fine for me and started into the actual sieving.[/QUOTE]

Me too.

Hello.

I've tried and I also get an error.

The error happens with version 1.34.5 x64 for Windows.
With 1.33 is OK.

I've tried with different ggnfs and it doesn't make any difference, the problem should be yafu.

I attach the logs and error.
I haven´t included the binary because it's bigger than 1MB even compressed.

Hmmm, two people independently confirm that Yafu runs just fine with the number in question. I'm starting to think this may not be a YAFU issue...

:smile:

Ok, I'll see if rebooting and changing YAFU.ini makes any difference. Probably my tired old computer wearing out.

ETA: Nope, still crashes on poly with skew=2.0487, c6=625, c0=46208. Y1, Y0 and "m" are generated as well, but "n" is not there. YAFU appears to hang up there.

[QUOTE=swellman;385263]Hmmm, two people independently confirm that Yafu runs just fine with the number in question. I'm starting to think this may not be a YAFU issue...

:smile:

Ok, I'll see if rebooting and changing YAFU.ini makes any difference. Probably my tired old computer wearing out.[/QUOTE]

Could be a windows only thing. I tested with linux. I'm not sure why there would be a difference, but it wouldn't be the strangest bug yet if so.

I ran it on Windows 7 64-bit, albeit in MinGW-64.

Edit: Version is 1.34.5 64-bit.

Wombatman - did you test in Windows 64?

bsquared, do you have VM or some such tools to emulate windows?

I can try it tonight on another win box later tonight.

eta: thanks wombatman. Ignore the thumbs down symbol - not sure how it got there and I can't seem to erase it!

I've verified the crash on a windows box. Thanks for the report!