* Add GDB helper script
Pretty printing of some common argument types
Need to add a line to ~/.gdbinit
> add-auto-load-safe-path /path/to/base/checkout/
afterwards verify at GDB shell with
> info auto-load python-scripts
> info pretty-printer
Tested with GDB 16.3 circa Debian 13
Add $rcast(dbCommon) to up-cast
Add $record("name") to lookup record
Add $elln(ELLLIST,#) to index into list
../rec/biRecord.c:191:42: warning: argument to ‘sizeof’ in ‘strncpy’
call is the same expression as the source; did you mean to use the
size of the destination? [-Wsizeof-pointer-memaccess]
191 | strncpy(pstring,prec->znam,sizeof(prec->znam));
| ^
Use memcpy instead of snprintf.
STATIC_ASSERT is added to ensure znam and onam are sized enough.
Debugging a problem and looking at the message
recGblDbaddrError: dbPut: Request type is 0 Illegal Database Request Type...
does not help very much: request type 0 is a legal value.
Improve the message to show the field type as well:
recGblDbaddrError: dbPut: dbrType = 0 field_type = DBF_INLIK (14)...
Do the same for both dbPut and dbGet.
RTEMS performs a few early errlogPrintf calls. This initialises
the errlog buffers to some default values blocking certain tests
from re-initialising the error log later.
After connectCallback, need to wait for up to three
concurrent actions. Native and string subscriptions,
as well as GET of metadata.
Complicated because event_handler_args does not identify
the evid.
see 717d69e1fc
The DST characteristics of the POSIX EST5EDT and CST6CDT timezones
depend on whether the implementation uses the built-in POSIX definition
or reads an updated version from the tzdata files, and for POSIX
timezones, there is no specified behavior [1].
To avoid any plaform-specific behavior, we can specify the desired DST
ourselves. We used the timezone values available in
configure/CONFIG_SITE_ENV, which already included DST information, and
means the tests are consistent with our own usage.
[1] https://www.openwall.com/lists/musl/2024/03/05/2
* skeleton for implementation of dbCreateRecord iocsh exposure
* Add functionality of dbCreateRecordCallFunc
Includes adding dependancy to iocInit.h and a new error type in dbStaticLib.h
* Fix error message for case when adding record to IOC post init
* add new error message for when no record name is passed and check for empty strings
* add release note for dbCreateRecord IOC shell command
* fix issues from codeql in release notes
* fix documentation md based on codacy styling
Added debug messages for client verification.
With -d the repeater shows client events, e.g.
$ caRepeater -d
CA Repeater: Attached and initialized
New client on port 60307
Verified 1 active clients
New client on port 52541
Verified 2 active clients
Client on port 60307 refused message
Deleted client on port 60307
Client on port 52541 refused message
Deleted client on port 52541
^C
Running "caRepeater -dd" also shows beacon forwarding and
individual client verification:
$ caRepeater -dd
CA Repeater: Attached and initialized
New client on port 49968
Client on port 49968 is alive
Verified 1 active clients
Sent to port 49968
Sent to port 49968
Sent to port 49968
New client on port 65377
Sent to port 49968
Client on port 49968 is alive
Client on port 65377 is alive
Verified 2 active clients
Sent to port 49968
Sent to port 65377
Sent to port 49968
Sent to port 65377
Client on port 49968 refused message
Deleted client on port 49968
Sent to port 65377
Sent to port 65377
Client on port 65377 refused message
Deleted client on port 65377
^C
Michael Davidsaver
zimoch