Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Valgrind plugin

<< < (8/9) > >>

killerbot:
Thanks for reporting, I will fix this. It seems the new Valgrind wants an xml file to be specified.

killerbot:
alright I know what to do.

Off course the fun is i will have to check valgrind versions since the changes valgrind has are not backwards compatible.

Old command :

--- Code: ---valgrind --leak-check=yes --xml=yes ./DeleteMe
--- End code ---

New command :

--- Code: ---valgrind --leak-check=yes --xml=yes --xml-file=test.xml ./DeleteMe
--- End code ---

Unfortunately the option 'xml-file=test.xml' will be flagged as an error by the old valgrind (valgrind: Bad option '--xml-file=test.xml'; aborting.).

Will start working on it soon.

oBFusCATed:
Why not use:

--- Code: ---valgrind --leak-check=yes --xml=yes --xml-fd=1 ./test_cb_stl_debug

--- End code ---

 --xml-fd=1 -> should mean use file that is the standard output

killerbot:
could work too, yes.
But the special version check logic will be needed, since also this will cause an error on pre 3.5.0 versions of valgrind.

But I think, putting it in a real file will be better, that way regular program output on stdout can not mix with the xml output parts.

Have already coded the change, test session should be carried out tomorrow.

oBFusCATed:
C::B project - debugger branch:

Valgrind -> Run Valgrind::MemCheck says:
"You need to have an (executable) target in your open project before using the plugin!"

I've tried  targets: "All" and "src"

Navigation

[0] Message Index

[#] Next page

[*] Previous page