https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #8 from Gerrit Code Review ---
Change 30362 merged by Pascal Quantin:
RTP.ED-137: Memleak fixed
https://code.wireshark.org/review/30362
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
Pascal Quantin changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #7 from Gerrit Code Review ---
Change 30362 had a related patch set uploaded by Jirka Novak:
RTP.ED-137: Memleak fixed
https://code.wireshark.org/review/30362
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #6 from Peter Wu ---
(In reply to Jiri Novak from comment #5)
> I prepared patch based on your idea, but it doesn't work. I mean it creates
> segfault, because code is:
>
> tmp = rel_time_to_secs_str(NULL, _time);
>
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #5 from Jiri Novak ---
Hi Peter,
> So are both times effectively relative?
yes, they are.
I prepared patch based on your idea, but it doesn't work. I mean it creates
segfault, because code is:
tmp =
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #4 from Peter Wu ---
> Even one branch is "ntp based", it doesn't mean time is ntp/absolute. It
> just says where send got time reference. Time in packet is just counter
> derived from ntp, but it don't contain all ntp
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
--- Comment #3 from Jiri Novak ---
Hi Peter,
yes, this fix will work.
You are right that both branches are same. I created the first one without
sample data and then added content of second one, but didn't cleaned the code.
Even
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15231
Peter Wu changed:
What|Removed |Added
Summary|[oss-fuzz] ASAN: 22 byte(s) |[oss-fuzz] ASAN: 22 bytes
