caget -0x output on 64-bit
Bug #1699332 reported by
Andrew Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| EPICS Base | Status tracked in 7.0 | |||||
| 3.14 |
Fix Released
|
Undecided
|
Unassigned | |||
| 3.15 |
Fix Released
|
Undecided
|
Unassigned | |||
| 3.16 |
Fix Released
|
Undecided
|
Unassigned | |||
| 7.0 |
Fix Released
|
Low
|
Andrew Johnson | |||
Bug Description
The output from 'caget -0x <pv>' is printed as a 64-bit quantity when run on a 64-bit system, even though the underlying DBF_LONG type is only 32-bits wide. This is only visible when the pv is negative:
tux% caget -0x anj:exit.DISV
anj:exit.DISV 0xFFFFFFFFFFFFFFFF
A similar problem occurs with the '-0o' option, and camonitor is also similarly affected.
I'm committing a fix to tool_lib.c on the 3.14 branch.
| Changed in epics-base: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
