I agree that there is a problem. I didn't verify whether this (or any other) factor is actually correct, but mprime segfaulted when finishing the exponent. Konsole snippet follows:

Code:

[Worker #1 Aug 14 01:16] Stage 2 GCD complete. Time: 246.293 sec.
[Worker #1 Aug 14 01:16] P-1 found a factor in stage #2, B1=410000, B2=11070000.
[Worker #1 Aug 14 01:16] M34400389 has a factor: 9541285631068389553
Segmentation fault (core dumped)
kossy@leela:~/leela$ ./__start
[Main thread Aug 16 13:28] Mersenne number primality test program version 25.6
[Comm thread Aug 16 13:28] Sending result to server: UID: ckdo/leela, M34400389 has a factor: 9541285631068389553, AID: 5678875EA392BC568ED714947B23CE86
[Comm thread Aug 16 13:28]
[Main thread Aug 16 13:28] Starting worker threads.
[Worker #1 Aug 16 13:28] Work thread starting
[Worker #3 Aug 16 13:28] Work thread starting
[Worker #4 Aug 16 13:28] Work thread starting
[Worker #2 Aug 16 13:28] Work thread starting
[Worker #4 Aug 16 13:28] Optimal P-1 factoring of M34401967 using up to 1792MB of memory.
[Worker #1 Aug 16 13:28] Optimal P-1 factoring of M34400389 using up to 1792MB of memory.
[Worker #1 Aug 16 13:28] Assuming no factors below 2^68 and 2 primality tests saved if a factor is found.
[Worker #2 Aug 16 13:28] Optimal P-1 factoring of M34400603 using up to 1792MB of memory.
[Worker #2 Aug 16 13:28] Assuming no factors below 2^68 and 2 primality tests saved if a factor is found.
[Worker #4 Aug 16 13:28] Assuming no factors below 2^68 and 2 primality tests saved if a factor is found.
[Worker #3 Aug 16 13:28] Optimal P-1 factoring of M34401827 using up to 1792MB of memory.
[Worker #3 Aug 16 13:28] Assuming no factors below 2^68 and 2 primality tests saved if a factor is found.
[Comm thread Aug 16 13:28] PrimeNet success code with additional info:
[Comm thread Aug 16 13:28] CPU credit is 1.382725 GHz-days.

Notice that it did in fact start the same exponent again (which I happened to notice only hours later, duh!)...