Hi Charles,
> Here's a stack trace for two different cases:
>
> * Running rtapi_app using electric fence
>
> * Running hal_cmd and following the child on fork (the crash happens in
> rtapi_app, launched by hal_cmd)
>
> Of possible interest:
> If you run rtapi_app on it's own without electric fence, it doesn't crash.
I've done both these scenarios.
halcmd and following the child, the crash happened in rtapi_app; that's
why I've been focusing on it so intently.
Without electric fence, running rtapi_app on its own, I could get it to
segfault only sometimes. It would segfault more if running in 'record'
mode, probably because it missed more deadlines and spewed more output,
tickling the bug more.
Another trick is to run rtapi_app in gdb, then from a shell, call halrun
-U. If rtapi_app hasn't crashed before this point, it has always
segfaulted here. These crashes have always occurred in malloc() for me,
whereas the early crash with rtapi_app+EF occurs in vfprintf().
John
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
