Fixes #32

[vhqtvn]

Fixes #32

An error might not contain xwhat, only what. This fix assumes that these errors are not a leaking error.

An example one in my case:

<error>
  <unique>0x0</unique>
  <tid>1</tid>
  <kind>SyscallParam</kind>
  <what>Syscall param statx(file_name) points to unaddressable byte(s)</what>
  <stack>REMOVED</stack>
  <auxwhat>Address 0x0 is not stack'd, malloc'd or (recently) free'd</auxwhat>
</error>

[jfrimmel]

Thank you for the contribution! Just ignore the failing clippy CI test.

I just have a nitpick and a question: do you basically change the code to always have an xwhat-error, which is possibly empty?

[jfrimmel]

Suggested change

	.map(|o_: xml::Output| {
	let mut o = o_;
	.map(|o: xml::Output| {

Furthermore, couldn you please rename all os to output?

[vhqtvn]

Yes i took a quick look on serde and cant find a quick way to case-typing parsing so i just let it to be empty on failure. And then in the reporter I let it filter out the errors that doesnt have leaking info (filter(|e| e.resources.bytes > 0 || e.resources.blocks > 0)).

[jfrimmel]

Thank you for your contribution, I'll make a release soon.

[Anders429]

@jfrimmel Any chance we could get a release on crates.io that includes this change? I've had this issue come up for me, and it looks like a new release with this PR included would fix it :)

[jfrimmel]

Oh, well, I've simply forgot doing it... I'll need an automatic release workflow in this repository...

I've published version 2.0.2 containing this fix.