> but some threads exit with 0 and some with 1. Is it Ok?
The function _beginthreadex() is used by epicsThreadCreate() to make a new
thread on windows. The new thread jumps into an epics internal wrapper
function that calls the user's function. It should always be returning one.
So I dont know why visual C++ is reporting different return codes. This
might be a feature of an internal wrapper employed by _beginthreadex().
Jeff
> -----Original Message-----
> From: Liyu, Andrei [mailto:[email protected]]
> Sent: Thursday, January 15, 2004 9:48 AM
> To: [email protected]
> Subject: Epics server stop
>
>
> Hi,
>
> I try to use Epics 3.14.4 under Windows for win32-x86.
> I work with Epics from Visual C++ environment :)
> I see how much threads Epics uses but some threads exit with
> 0 and some
> with 1.
> Is it Ok?
>
> ==================
> The thread 0xA04 has exited with code 1 (0x1).
> The thread 0xC48 has exited with code 1 (0x1).
> The thread 0x1B4 has exited with code 1 (0x1).
> The thread 0xFB4 has exited with code 1 (0x1).
> The thread 0xB88 has exited with code 1 (0x1).
> The thread 0xCD8 has exited with code 1 (0x1).
> The thread 0xB40 has exited with code 1 (0x1).
> The thread 0x888 has exited with code 1 (0x1).
> The thread 0xF24 has exited with code 1 (0x1).
> The thread 0xE74 has exited with code 1 (0x1).
> The thread 0x840 has exited with code 1 (0x1).
> The thread 0xA8C has exited with code 1 (0x1).
> The thread 0x960 has exited with code 1 (0x1).
> The thread 0xFC4 has exited with code 1 (0x1).
> The thread 0xB24 has exited with code 1 (0x1).
> The thread 0x6D4 has exited with code 1 (0x1).
> The thread 0xE7C has exited with code 1 (0x1).
> The thread 0x818 has exited with code 1 (0x1).
> The thread 0x97C has exited with code 1 (0x1).
> The thread 0xE88 has exited with code 1 (0x1).
> The thread 0x920 has exited with code 1 (0x1).
> The thread 0x8F4 has exited with code 1 (0x1).
> The thread 0xC04 has exited with code 1 (0x1).
> The thread 0xF50 has exited with code 1 (0x1).
> The thread 0xB30 has exited with code 1 (0x1).
> The thread 0xD20 has exited with code 1 (0x1).
> The thread 0xA48 has exited with code 0 (0x0).
> The thread 0xBFC has exited with code 0 (0x0).
> The thread 0xFC8 has exited with code 0 (0x0).
> The thread 0x3A0 has exited with code 0 (0x0).
> The thread 0xE28 has exited with code 0 (0x0).
> The thread 0xF44 has exited with code 0 (0x0).
> The thread 0x8E0 has exited with code 0 (0x0).
> The thread 0x74 has exited with code 0 (0x0).
> The thread 0xBF8 has exited with code 0 (0x0).
> The thread 0x958 has exited with code 0 (0x0).
> The thread 0x13C has exited with code 0 (0x0).
> The thread 0x900 has exited with code 0 (0x0).
> The thread 0x3B0 has exited with code 0 (0x0).
> The thread 0xFEC has exited with code 0 (0x0).
> The thread 0x5AC has exited with code 0 (0x0).
> The thread 0xB70 has exited with code 0 (0x0).
> The thread 0xCD4 has exited with code 0 (0x0).
> The thread 0xBF0 has exited with code 0 (0x0).
> The thread 0xA20 has exited with code 0 (0x0).
> The thread 0xE20 has exited with code 0 (0x0).
> The thread 0xB68 has exited with code 0 (0x0).
> The thread 0x91C has exited with code 0 (0x0).
> The thread 0x980 has exited with code 0 (0x0).
> ====================
> Thank,
> Andrei.
>
- References:
- Epics server stop Liyu, Andrei
- Navigate by Date:
- Prev:
Re: ? monitor and waveform record Steven Hartman
- Next:
RE: Epics server stop Liyu, Andrei
- 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:
Epics server stop Liyu, Andrei
- Next:
RE: Epics server stop Liyu, Andrei
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·