Bug#848881: [gpart] Floating point exception when scanning

2016-12-20 Thread Ingo Jürgensmann
Am 20.12.2016 um 18:24 schrieb Baruch Even : > Can you please run it under gdb and capture the output of the command: > bt > bt full Reading symbols from /usr/sbin/gpart...(no debugging symbols found)...done. (gdb) r Starting program: /usr/sbin/gpart -f /dev/lv/Elite3 Program

Bug#848881: [gpart] Floating point exception when scanning

2016-12-20 Thread Baruch Even
Can you please run it under gdb and capture the output of the command: bt bt full Baruch On Tue, Dec 20, 2016, 18:32 Eriberto Mota wrote: > Control: severity 848881 important > > Hi, > > Adding Baruch (upstream) in Cc. > > I downgraded the severity to important because

Bug#848881: [gpart] Floating point exception when scanning

2016-12-20 Thread Eriberto Mota
Control: severity 848881 important Hi, Adding Baruch (upstream) in Cc. I downgraded the severity to important because this bug is not grave (maybe it could be normal). Baruch, any idea? Regards, Eriberto 2016-12-20 11:33 GMT-02:00 Ingo Juergensmann : > Package:

Bug#848881: [gpart] Floating point exception when scanning

2016-12-20 Thread Ingo Juergensmann
Package: gpart Version: 1:0.3-3 Severity: grave --- Please enter the report below this line. --- Hi! When trying to examine a volume on LVM, I get a floating point exception quite instantly: # strace -f gpart -f /dev/lv/Elite3 execve("/usr/sbin/gpart", ["gpart", "-f", "/dev/lv/Elite3"], [/* 59