Experimental Physics and
Industrial Control System

Steven <[email protected]> · Fri, 10 Oct 2014 16:05:46 -0400

Hello Epics community

This core was cause d by me. There is no problem with epics. Mark was using a file that I modified. 

I am sorry for taking everyone's valuable time.  

Sent from my iPhone

On Oct 9, 2014, at 4:04 PM, "Konrad, Martin" <[email protected]> wrote:

> Hi Mark,
>> If you can't, take a look at how much stack space your
>> Process1_routine subroutine needs, running out of stack space is one
>> possible cause for this kind of strange behaviour in addition to the
>> usual kinds of problems. A full stack trace for all threads when the
>> crash happens would also help us help you (type 'thread apply all bt'
>> in gdb).
> Keep in mind that the stack trace could be corrupted. You might want to 
> run with a trivial subroutine for testing.
> 
> In addition to that it's always a good idea to write a short test 
> program that calls the subroutine function with some test values. You 
> can run this test program with
> 
> valgrind --tool=memcheck <your_test_program>
> 
> to see if it is writing to memory it should not write to.
> 
> Regards,
> 
> Martin
> 
> -- 
> Martin Konrad
> Control System Engineer
> Facility for Rare Isotope Beams
> Michigan State University
> 640 South Shaw Lane
> East Lansing, MI 48824-1321, USA
> Tel. 517-908-7253
> Email: [email protected]
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System