It is possible the file is corrupted.  Please try to run “wb_command 
-file-information  <name-of-file>” on the file and see if that works.

On Dec 12, 2017, at 12:20 PM, Marta Moreno 
<[email protected]<mailto:[email protected]>> wrote:

Thanks.

Yes, I can load spec files but when trying to see functional connectivity maps 
for the specific subject it crashes. I can load other type of files, i.e., seed 
used. This is the first time I cannot see this file, before I was able to do so 
without crashing. I have downloaded workbench v1.2.3. now but the problem 
persists. The only change I had these past weeks was the MATLAB_R2017b.


On Dec 12, 2017, at 1:12 PM, Harwell, John 
<[email protected]<mailto:[email protected]>> wrote:


Hi Marta,

Does wb_view start up if you do not try to load any files?  Is this the first 
time you have run wb_view on this Mac?

Do you know which file is causing the crash?  You could use File Menu —> Open 
File and try opening just a surface file.


John Harwell


On Dec 12, 2017, at 11:25 AM, Marta Moreno 
<[email protected]<mailto:[email protected]>> wrote:

Dear experts,

I am getting an error any time I am trying to open file in wb_view. Any idea 
how to solve this problem?

Thanks,

-L

Error attached below:

Process:               wb_view [56364]
Path:                  
/usr/local/workbench-new/bin_macosx64/../macosx64_apps/wb_view.app/Contents/MacOS/wb_view
Identifier:            workbench
Version:               1.1.1 (1.1.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [56362]
Responsible:           wb_view [56364]
User ID:               501

Date/Time:             2017-12-12 12:21:10.852 -0500
OS Version:            Mac OS X 10.12.5 (16F73)
Report Version:        12
Anonymous UUID:        D5FF43E5-1CCA-5E9C-C5AF-22ACAE67AFE8


Time Awake Since Boot: 2700000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]


_______________________________________________
HCP-Users mailing list
[email protected]<mailto:[email protected]>
http://lists.humanconnectome.org/mailman/listinfo/hcp-users




_______________________________________________
HCP-Users mailing list
[email protected]
http://lists.humanconnectome.org/mailman/listinfo/hcp-users

Reply via email to