Experimental Physics and Industrial Control System
|
Hi Heinz,
Are you building as windows-x64 or windows-x64-static architecture? I was just wondering if the initHook() was running before the
winsock library was initialised, which needs to be done by a call to osiSockAttach() somewhere. The DLL based epics build (windows-x64) is a bit more forgiving about this as it loads winsock from WS2_32.DLL which often seems to self-initialise, but I’ve generally
found that static EPICS windows builds do not work if you try and use sockets before a call to osiSockAttach() has happened
Regards,
Freddie
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Mark Rivers via Tech-talk
Sent: 30 January 2024 14:43
To: EPICS Tech Talk <tech-talk at aps.anl.gov>; Heinz Junkes <junkes at fhi-berlin.mpg.de>
Subject: Re: known problem with the reccaster on Windows?
What happens if you build ADLightField without reccaster?
Have you tried running the ADSimDetector, also built with reccaster?
If you build with the windows-x64-debug architecture then you can debug with Visual Studio and perhaps get more information on what it happening in
doCasterTCPPhase.
From: Tech-talk on behalf of Heinz Junkes via Tech-talk
Sent: Tuesday, January 30, 2024 5:11 AM
To: EPICS Tech Talk
Subject: known problem with the reccaster on Windows?
Hi,
I'm trying to get the autosave working on an IOC running on Windows.
Unfortunately the IOC hangs at iocInit(?) and I can't debug any further.
Unfortunately, I can't figure it out on Windows (I simply have zero experience with it) and maybe I'm just being stupid.
There is an IOC in the areadetector for the Lightfield application. When starting the IOC we get the following error message:
restore: Can t open save file. locRun: All initialization complete
epicsSocketDestroy: failed to close a socket because "An operation was attempted on someth ing that is not a socket. "
epicsSocketDestroy: failed to close a socket because "An operation was attempted on someth ing that is not a socket. "
casterInit failed to create shutdown socketThread win994 (00000112429708B0) can't proceed, suspending.
Dumping a stack trace of thread 'win994':
[ 00007FFF05B709CF](epicsStackTrace+0x7f)
[ 00007FFF05B5E934] (cantProceed+0x94)
[ 00007FFF128044DB] (doCasterTCPPhase+0x7fb)
[ 00007FFF05B58B85] (initHookAnnounce+0xc5)
[ 00007FFF0539EF71] (iocRun+0x151)
[ 00007FFF0539F152](miscIocRegister+0x162)
[ 00007FFF05B56E57](iocsh+0x1127)
[ 00007FF6A2D63B43]
[ 00007FF6A2D62B90]
[ 00007FFF2DCF7344] (BaseThreadInitThunk+0x14)
[ 00007FFF2F6C26B1]RtlUserThreadStart+0x21)
We are running reccaster …
Is this a known problem with the reccaster on Windows?
Danke Heinz
|
- Replies:
- Re: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- References:
- known problem with the reccaster on Windows? Heinz Junkes via Tech-talk
- Re: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- Navigate by Date:
- Prev:
Re: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- Next:
Re: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- 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: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- Next:
Re: known problem with the reccaster on Windows? Mark Rivers via Tech-talk
- 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>
|
ANJ, 30 Jan 2024 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|