On 1/22/14 11:33 , Curtis Dutton wrote:
> Does anyone know what may have caused this?
>
> So I'm running the circular arc blend beta from Roberts github repository.
> I'm running a build based on commit
> 8acb5e68a4e9c03b191555f912de53e639576dec
>
>
> I'm not sure if this is related to circular arc blend or just latest
> linuxcnc master code.
>
> Attached is the backtrace. I was running a call (in the command window) "o
> <tool_change> call" which is a simple program to touch a tool probe after a
> manual change. It had just finished that subroutine when milltask died.
>
> Attached is the backtrace.

Please open a bug against 2.6 in the tracker for this (include the 
backtrace and your tool_change.ngc file):  http://sf.net/p/emc/bugs

Is the problem repeatable?

Were you doing anything weird like moving or editing the tool_change.ngc 
file, or maybe a file it was calling, while running?

There's definitely some sketchy file handling code in master, in 
interp_o_word.c's execute_return() function.  Not sure if that's related 
to this segfault or just innocently located near where the problem happened.

Looks like Michael was there last, would you mind taking a look?  I'm 
thinking specifically of the unchecked file re-opening logic just before 
this segfault.


-- 
Sebastian Kuzminsky

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to