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]
- Replies:
- RE: Fanout to Sub Records in a Different IOC Causes Core Dump Poff, Mark A
- Re: Fanout to Sub Records in a Different IOC Causes Core Dump Steven
- References:
- RE: Fanout to Sub Records in a Different IOC Causes Core Dump Poff, Mark A
- Navigate by Date:
- Prev:
Re: Fanout to Sub Records in a Different IOC Causes Core Dump Andrew Johnson
- Next:
Re: MCA and WAN connection Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Fanout to Sub Records in a Different IOC Causes Core Dump Andrew Johnson
- Next:
RE: Fanout to Sub Records in a Different IOC Causes Core Dump Poff, Mark A
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|