Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Valgrind plugin
Jenna:
--- Quote from: MortenMacFly on July 14, 2008, 02:31:51 pm ---
--- Quote from: jens on July 14, 2008, 01:22:25 pm ---I meant the entry wher I can find the disabled and enabled status [...]
And that could not happen for Valgrind because of the crash.
--- End quote ---
Probably due to the crash this setting was not saved. I had the same issue with the svnInside plugin. I disabled the plugin to avoid crashes on exit of C::B. But these settings were always lost until I really removed this plugin.
--- End quote ---
Afaik the "real" writing is done when C::B closes correctly. If C::B crashes all changes to default.conf are lost.
I can manually disable Valgrind-plugin, if I edit default.conf and set the value for "VALGRIND" to "0".
If I have done this, I can enable Valgrind-plugin from inside C::B, but if I try to redisable it, the crash occurs again.
There is another issue, when I try to check a program on a
killerbot:
some part of your last post got lost ...
Jenna:
--- Quote from: killerbot on July 14, 2008, 03:33:09 pm ---some part of your last post got lost ...
--- End quote ---
--- Quote from: jens on July 14, 2008, 03:03:16 pm ---There is another issue, when I try to check a program on a
--- End quote ---
here it should continue:
But, the error is not related to what I thought before (so I can't continue my sentence from above).
Nevertheless it still occurs:
I have a workspace that includes a program and a shared library.
The output directory of the shared library is the same as the one of the program.
If I debug, the debuggerplugin sets the "LD_LIBRARY_PATH" correctly, but the Valgrind-plugin seems not to set it, and so valgrind does not find the library.
The error is not in the "Valgrind messages" list-logger, it's only (more or less hidden) in the xml-output.
The parent-element of the error-message is "<valgrindoutput>". I think, that might be the cause that it is not shown in the list-logger.
killerbot:
the valgrind plug-in is currently very simple, I have tested it on simple applications.
Basically it is just calling valgrind with some parameters, one of those parameters is the name of the application valgrind is ordered to check.
Could you attach valgrind plugin log output.
Jenna:
Here it is.
It seems to be an error message of my executable (or better from linux), not from Valgrind.
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version