Just run:
source /usr/local/freesurfer/nmr-dev-env 

> On May 6, 2014, at 10:34 AM, "[email protected]" 
> <[email protected]> wrote:
> 
> I have not tried dev version. Can you please let me know how I can load that?
> 
>> Have you tried dev version?
>> 
>> On May 6, 2014, at 10:15 AM, "[email protected]"
>> <[email protected]> wrote:
>> 
>>> Hello All,
>>> 
>>> Any idea why freeview fails to open? Below I have included the terminal
>>> output.
>>> 
>>> I have checked my quota and I have plenty of available memory. I also
>>> tried running the 2 options (-start_in_debugger  and
>>> -on_error_attach_debugger), but these were not recognized. I was next
>>> going to attempt to configure, but I fear I may do more damage if I
>>> start
>>> messing around with cmds that I do not understand.
>>> 
>>> Thank you for the assistance!
>>> 
>>> Jacob
>>> 
>>> 
>>> [purkinje:mri] (nmr-stable53-env) freeview
>>> [0]PETSC ERROR:
>>> ------------------------------------------------------------------------
>>> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
>>> probably memory access out of range
>>> [0]PETSC ERROR: Try option -start_in_debugger or
>>> -on_error_attach_debugger
>>> [0]PETSC ERROR: or see
>>> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC
>>> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to
>>> find memory corruption errors
>>> [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link,
>>> and
>>> run
>>> [0]PETSC ERROR: to get more information on the crash.
>>> [0]PETSC ERROR: --------------------- Error Message
>>> ------------------------------------
>>> [0]PETSC ERROR: Signal received!
>>> [0]PETSC ERROR:
>>> ------------------------------------------------------------------------
>>> [0]PETSC ERROR: Petsc Release Version 2.3.3, Patch 13, Thu May 15
>>> 17:29:26
>>> CDT 2008 HG revision: 4466c6289a0922df26e20626fd4a0b4dd03c8124
>>> [0]PETSC ERROR: See docs/changes/index.html for recent updates.
>>> [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.
>>> [0]PETSC ERROR: See docs/index.html for manual pages.
>>> [0]PETSC ERROR:
>>> ------------------------------------------------------------------------
>>> [0]PETSC ERROR: Unknown Name on a linux-gnu named
>>> purkinje.nmr.mgh.harvard.edu by jacobml Tue May  6 10:07:13 2014
>>> [0]PETSC ERROR: Libraries linked from
>>> /autofs/space/lyon_006/pubsw/Linux2-2.3-x86_64/packages/petsc/2.3.3-p13/src/petsc-2.3.3-p13/lib/linux-gnu-c-opt
>>> [0]PETSC ERROR: Configure run at Tue Aug 10 15:01:59 2010
>>> [0]PETSC ERROR: Configure options --with-debugging=no --with-cc=gcc
>>> --with-fc=g77 --download-f-blas-lapack=0 --download-mpich=1 --with-mpi=1
>>> --with-x=0 --with-gnu-copyright-code=0 --with-shared=0 COPTFLAGS=-O3
>>> CXXOPTFLAGS=-O3 FOPTFLAGS=-O3
>>> [0]PETSC ERROR:
>>> ------------------------------------------------------------------------
>>> [0]PETSC ERROR: User provided function() line 0 in unknown directory
>>> unknown file
>>> [unset]: aborting job:
>>> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
>>> _______________________________________________
>>> Freesurfer mailing list
>>> [email protected]
>>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>> 
>> 
>> _______________________________________________
>> Freesurfer mailing list
>> [email protected]
>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
> 
> _______________________________________________
> Freesurfer mailing list
> [email protected]
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
> 
> 

_______________________________________________
Freesurfer mailing list
[email protected]
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.

Reply via email to