Re: [Freesurfer] mri_info crashing (bits stored vs bits allocated?)

2013-03-21 Thread Bruce Fischl
Hi John

apparently Nick already fixed this bug. If you send us the details of 
your hardware/software environment we'll send you updated mri_info and 
mri_convert binaries

cheers
Bruce
On Wed, 20 Mar 2013, Ostuni, John (NIH/NINDS) [E] 
wrote:

> We have a data set that mri_info cannot work with.
>
> We've tried multiple architectures and freesurfer versions, but mri_info 
> either crashes with segmentation fault or generates errors such as
> *** glibc detected *** mri_info: free(): invalid pointer: 0x006b 
> ***
>
> One feature of the data set is that the bits stored(12) is different than the 
> bits allocated(16).
> Could this be the problem?
>
> I have an anonymized version of the data set I can upload if that helps.
>
> Thanks for any assistance,
>   John
>
>
>
> ___
> Freesurfer mailing list
> Freesurfer@nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>
>
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.



Re: [Freesurfer] mri_info crashing (bits stored vs bits allocated?)

2013-03-20 Thread Knut J Bjuland
HI

I have similar problem and filled a bug report at.


Product: Fedorahttps://bugzilla.redhat.com/show_bug.cgi?id=905638  Patsy
Franklin  changed: What |Removed |Added

Flags|needinfo?(pfrankli@redhat.c  | |om) |
Flags|needinfo?(pfrankli@redhat.c  | |om) | --- Comment #27 from Patsy
Franklin  --- The most immediate solution is for
the application to be changed to use a compliant crypt salt value. After
further investigation, we found that the application is passing
unsupported, nonstandard salt to crypt(). This will result in crypt()
returning NULL and setting errno to EINVAL. It does not appear that the
application is checking for a NULL return value from crypt. It also
appears that the application is using this NULL return value in a
subsequent function call resulting in a segmentation fault. Previously
glibc would accept unsupported salt values, but newer versions of the
library have become stricter. We are currently reviewing the
implementation to see if the accepted salt values can be expanded while
still meeting our standards compliance requirements.
--

Knut J











On 03/20/2013 09:59 PM, Bruce Fischl wrote:
> Hi John
>
> if you email it to me I'll take a look
> Bruce
> On Wed, 20 Mar 2013, Ostuni, John
> (NIH/NINDS) [E] wrote:
>
>> We have a data set that mri_info cannot work with.
>>
>> We've tried multiple architectures and freesurfer versions, but mri_info 
>> either crashes with segmentation fault or generates errors such as
>> *** glibc detected *** mri_info: free(): invalid pointer: 0x006b 
>> ***
>>
>> One feature of the data set is that the bits stored(12) is different than 
>> the bits allocated(16).
>> Could this be the problem?
>>
>> I have an anonymized version of the data set I can upload if that helps.
>>
>> Thanks for any assistance,
>>John
>>
>>
>>
>> ___
>> Freesurfer mailing list
>> Freesurfer@nmr.mgh.harvard.edu
>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>>
>>
>>
> ___
> Freesurfer mailing list
> Freesurfer@nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>
>
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine 
> at
> http://www.partners.org/complianceline . If the e-mail was sent to you in 
> error
> but does not contain patient information, please contact the sender and 
> properly
> dispose of the e-mail.
>
>
>

___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


Re: [Freesurfer] mri_info crashing (bits stored vs bits allocated?)

2013-03-20 Thread Bruce Fischl
Hi John

if you email it to me I'll take a look
Bruce
On Wed, 20 Mar 2013, Ostuni, John 
(NIH/NINDS) [E] wrote:

> We have a data set that mri_info cannot work with.
>
> We've tried multiple architectures and freesurfer versions, but mri_info 
> either crashes with segmentation fault or generates errors such as
> *** glibc detected *** mri_info: free(): invalid pointer: 0x006b 
> ***
>
> One feature of the data set is that the bits stored(12) is different than the 
> bits allocated(16).
> Could this be the problem?
>
> I have an anonymized version of the data set I can upload if that helps.
>
> Thanks for any assistance,
>   John
>
>
>
> ___
> Freesurfer mailing list
> Freesurfer@nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>
>
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.



[Freesurfer] mri_info crashing (bits stored vs bits allocated?)

2013-03-20 Thread Ostuni, John (NIH/NINDS) [E]
We have a data set that mri_info cannot work with.

We've tried multiple architectures and freesurfer versions, but mri_info either 
crashes with segmentation fault or generates errors such as
*** glibc detected *** mri_info: free(): invalid pointer: 0x006b ***

One feature of the data set is that the bits stored(12) is different than the 
bits allocated(16).
Could this be the problem?

I have an anonymized version of the data set I can upload if that helps.

Thanks for any assistance,
   John



___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.