Bug 1392166 - flirt from fsl after terminate called after throwing an instance of 'NEWMAT::SingularException'
Summary: flirt from fsl after terminate called after throwing an instance of 'NEWMAT::...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 24
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-05 13:25 UTC by Knut J BJuland
Modified: 2016-12-05 14:27 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-05 14:27:09 UTC
Type: Bug


Attachments (Terms of Use)

Description Knut J BJuland 2016-11-05 13:25:11 UTC
Description of problem:
flirt from fsl after terminate called after throwing an instance of 'NEWMAT::SingularException'. This did not happen with Fedroa 23

Version-Release number of selected component (if applicable):
2.23.1

How reproducible:
every time 

Steps to Reproduce:
1. flirt.fsl -ref /home/knutjbj/subjects/test/dmri/xfms/tmp.bbregister.7784/fslregister/refvol.fslregister.nii -in /home/knutjbj/subjects/test/dmri/xfms/tmp.bbregister.7784/fslregister/movvol.fslregister.nii -bins 256 -cost corratio -dof 6 -searchrx -90 90 -searchry -90 90 -searchrz -90 90 -verbose 0 -omat /home/knutjbj/subjects/test/dmri/xfms/tmp.bbregister.7784/reg.init.dat.fsl.mat -init /home/knutjbj/subjects/test/dmri/xfms/tmp.bbregister.7784/fslregister/fslmat0.trans.mat -schedule /usr/local/freesurfer/bin/flirt.newdefault.20080811.sch

2.
3.

Actual results:
crash with NEWMAT::SingularException

Expected results:
should not throw NEWMAT::SingularException

Additional info:

Comment 1 Florian Weimer 2016-11-05 16:01:55 UTC
Why do you think this is a glibc (or even Fedora) bug?

In any case, we need a reduced test case under a license that does not prohibit commercial use.

Comment 2 Knut J BJuland 2016-12-05 14:23:52 UTC
When I upgrade glibc this bug was resolved. I use Fedora 25 which is not affected by this bug.


Note You need to log in before you can comment on or make changes to this bug.