[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered
https://bugs.kde.org/show_bug.cgi?id=458212 --- Comment #5 from Jim Kuhn --- > Is using %p in the filename a satisfactory workaround? That's probably fine for cases where the multiple xml files can be easily post-processed, but I suspect there are a lot of consumers of this data that expect it to be in one file (Jenkins plugins, for one). Perhaps both options could be provided (legacy [single-file] and new [multi-file]) with a push to getting downstream consumers to use the new multi-file output. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered
https://bugs.kde.org/show_bug.cgi?id=458212
--- Comment #2 from Jim Kuhn ---
(In reply to Paul Floyd from comment #1)
[...]
> Can you provide a small testcase to reproduce?
#include
#include
int main(int argc, char** argv) {
if (!fork()) {
abort();
}
malloc(10); // something for memcheck
}
$ valgrind --trace-children=yes --xml=yes --xml-file=test.memcheck ./a.out
$ grep valgrindoutput test.memcheck
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered
https://bugs.kde.org/show_bug.cgi?id=458212 Jim Kuhn changed: What|Removed |Added OS|Other |Linux Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 458212] New: Bad XML produced when a fatal_signal is encountered
https://bugs.kde.org/show_bug.cgi?id=458212 Bug ID: 458212 Summary: Bad XML produced when a fatal_signal is encountered Product: valgrind Version: 3.19.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: jim.k...@gmail.com Target Milestone: --- When running valgrind on an executable that generates aborts (google test "death" tests), the resulting xml output contains redundant `` closing tags. This breaks downstream tools that ingest this xml. OBSERVED RESULT $ grep valgrindoutput exec.memcheck EXPECTED RESULT $ grep valgrindoutput exec.memcheck SOFTWARE/OS VERSIONS Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
