fouzhe

> `self.exit_status` is set to the second element of the tuple so why can't it be None? Is the status always guaranteed to be set? > > https://github.com/jtpereyda/boofuzz/blob/d47fe7905013d3f215f36f73f9fd6e06dee39ee5/boofuzz/utils/debugger_thread_simple.py#L155-L156 The second...

It depends on the logic of the process monitor. I didn't modify any logic of the process monitor. I just modified the log content when the target process exits.

@SR4ven Sorry for the delay. Yeah, I think an exit with code 0 should not be picked up as a test case failure.

Hi, @guedou Here is the code snippet of `Fuzz` https://github.com/secdev/scapy/blob/c17140a419e3e4496706faa1cb9753816a6c586b/scapy/packet.py#L2475-L2489 The `new_default_fields` in L2481 doesn't contain fields in `multiple_type_fields`: https://github.com/secdev/scapy/blob/c17140a419e3e4496706faa1cb9753816a6c586b/scapy/packet.py#L2466-L2468 Hence, we can clear `new_default_fields` after L2481, avoiding duplicate update...

Hi, @guedou @gpotter2 Take the `IFETlv` packet in `ife.py` for example: ```python class IFETlv(Packet): """ Parent Class interhit by all ForCES TLV strucutures """ name = "IFETlv" fields_desc = [...

This issue got assigned [CVE-2018-12109](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12109)

Could you please attach the input file and tell me the FLIF version?

@attritionorg @cfanatic Sorry for my late! `notify.json`: ``` { "unicast" : "172.19.0.2", "logging" : { "level" : "debug", "console" : "true", "file" : { "enable" : "false", "path" : "/tmp/vsomeip.log"...

@wikiped Thanks!

Yeah,I will try it! @ax3l Did you use the file I attached?