Hello,
The following is not fully on-topic because it's more a question related
to how to use valgrind in our case. But maybe others have had similar
questions or a solution...
We have fat application servers, written in C/C++ on top of a DBS
(PostgreSQL). These application servers offer the business logic in a
Library Management System to application clients, written in Java, and
used by the librarian staff of the institutions. Both, server and
client, communicate over a TCP/IP protocol, developed for this purpose
by us: the librarian works with client, the client sends business
oriented commands to the app server, this does its work in the DBS and gives
responses to the client.
We do valgrinding the server and from time to time valgrind detects a
problem, for example usage of not initialized memory access, or jumps
based on this, etc.
Sometimes it is very difficult to find the exact reason for valgrind's
complaint and one has to use a gdb and for this to redo what the server
was executing, or better what the librarian did exactly with the client
that caused the server to execute this particular piece of code and
with which data input.
At the moment we use the following "trick": the librarian runs in
parallel to the client on the desktop a second window with a "tail -f ..."
on valgrinds log file (STDOUT) and the full screen is recorded with
Microsoft teams functionality. So we can use the timestamps in the log
to go to the replay of the recording and can see what the user did
exactly, which data was entered and which button pressed etc.
Are there other ideas to bring together the valgrind log and the usage
of the application?
Thanks for reading this.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
