Floating point exception with certain log files

[mattdperkins]

Certain log files are causing an error - others work fine.

I'm using Swar plot manager.

./chiaplotgraph /home/matt/swar_logs/wd1a_2021-05-18_02_11_33_379563.log
Opened /home/matt/swar_logs/wd1a_2021-05-18_02_11_33_379563.log tmp dirname: /media/matt/wd1tb_1 frm dirname: /mnt/usb-External_USB3.0_DD56419883891-0:0-part1 Floating point exception (core dumped)

[stolk]

Can you run it through gdb?

$ gdb chiaharvestgraph

run plotfile where

On Tue, May 18, 2021 at 1:42 AM Matthew @.***> wrote:

Certain log files are causing an error - others work fine.

I'm using Swar plot manager https://github.com/swar/Swar-Chia-Plot-Manager.

./chiaplotgraph /home/matt/swar_logs/wd1a_2021-05-18_02_11_33_379563.log Opened /home/matt/swar_logs/wd1a_2021-05-18_02_11_33_379563.log tmp dirname: /media/matt/wd1tb_1 frm dirname: /mnt/usb-External_USB3.0_DD56419883891-0:0-part1 Floating point exception (core dumped)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stolk/chiaplotgraph/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADPE4GZ2BEI4IH27EWG34TTOISABANCNFSM45CB2TXQ .

-- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada @.***

[Atompeng]

I receive the same error for a specific log file (a completed file). The log file has a start of 00:10 and an end of 08:20

Program received signal SIGFPE, Arithmetic exception.
0x00005555555574f4 in average_plot_time () at chiaplotgraph.c:359
359             return total / num;
(gdb) where
#0  0x00005555555574f4 in average_plot_time () at chiaplotgraph.c:359
#1  0x00005555555577c5 in update_drivespace_info () at chiaplotgraph.c:400
#2  0x0000555555557c40 in update_image () at chiaplotgraph.c:489
#3  0x0000555555557fa3 in main (argc=2, argv=0x7fffffffdbb8) at chiaplotgraph.c:561

[stolk]

Thank you for reporting. This is now fixed. Run git pull to get latest, and then rebuild binary.

[mattdperkins]

Confirmed :) Ran it against all files for yesterday, including the ones that were known to be an issue.

Thanks!