A little bit more info:
When this function is called:
retval = rtapi_shmem_getptr(mem_id, &mem);
mem_id = 1. Upon return, mem = 0x0 and retval = 0.
So it seems the shared memory system doesn't work properly as mem should
never be set to zero. This is pretty much the limit of my debugging
abilities.
Andy
Andrew Ayre wrote:
> Thanks. It seg faults at line 2350 in hal_lib.c:
>
> static int init_hal_data(void)
> {
> /* has the block already been initialized? */
> if (hal_data->version != 0) {
>
> It appears that hal_data is NULL at this point. Here is the call stack:
>
> hal/utils/halcmd_main.c:195 (main)
> hal/utils/halcmd.c:109 (halcmd_startup)
> hal/hal_lib.c:2350 (hal_init)
>
> Andy
>
> Jeff Epler wrote:
>> A system call trace (produced by using "strace") or a backtrace at the
>> time of the segmentation fault (produced using "gdb") would be helpful
>> in pinpointing the location of the problem.
>>
>> You can find information how to use these utilities on many pages on the
>> internet.
>>
>> Jeff
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Emc-users mailing list
>> Emc-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-users
>>
>>
>>
>
--
Andy
PGP Key ID: 0x67090A54
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
