Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sequencer-2-2
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
epics-modules
sequencer-2-2
Commits
ed0310ae
Commit
ed0310ae
authored
13 years ago
by
benjamin.franksen
Browse files
Options
Downloads
Patches
Plain Diff
docs: added all the (at this time) known problems
parent
1f8f0a6e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
documentation/KnownProblems.txt
+23
-3
23 additions, 3 deletions
documentation/KnownProblems.txt
with
23 additions
and
3 deletions
documentation/KnownProblems.txt
+
23
−
3
View file @
ed0310ae
...
...
@@ -6,6 +6,8 @@ Known Problems
Known Problems in Release 2.1.5
-------------------------------
These are all fixed in the latest snapshot.
* Using pvPutComplete or pvGetComplete inside a when-clause may
result in a deadlock: the state set forever waits for the
completion even though the callback arrived.
...
...
@@ -17,8 +19,6 @@ Known Problems in Release 2.1.5
epics thread priorities are reversed (or ignored, as is typically
the case for soft IOCs running in user mode on Linux or Windows).
The latest snapshot has this bug fixed.
* In safe mode, if a variable is monitored and sync'ed, it can
happen that an event is detected with efTestAndClear
but the underlying variable still has the old value.
...
...
@@ -30,8 +30,28 @@ Known Problems in Release 2.1.5
clear the flag in the action block only after you have actually
got the new value.
A fix for this problem will appear in 2.1.6.
* The asynchronous versions of pvPut and pvGet built-in functions
do not behave correctly in case of connection loss. Particularly,
if connection is lost when waiting for completion, the state set
that issued the command will not be woken, so that it will wait
for the full timeout (the hard-coded 10 seconds).
Thanks to Daniel Keating for finding
this bug and pointing me in the right direction how to fix it.
* The compiler crashes when an assign clause lists more PVs than
the array contains elements.
* The compiler reports wrong line numbers (and could potentially
crash, though I did not experience this) when SNL or C code is
included with an un-escaped preprocessor #include command.
* In safe mode, anonymous PVs deviate from named PVs in the behaviour
of event flags: Normally, event flags for monitored PVs will be
set when entering the first state because of the first monitor event
we get from CA after connecting. This should be emulated for
anonymous PVs in order to restore the symmetry and so that named
and anonymous PVs can be interchanged at will (as claimed in the docs).
.. _Known_Problems_2.1.4:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment