Wireshark-bugs: [Wireshark-bugs] [Bug 8321] Incorrect RTP statistics (Lost Packets indication no
Evan Huus
changed
bug 8321
| What |
Removed |
Added |
| Status |
RESOLVED
|
CONFIRMED
|
| Resolution |
FIXED
|
---
|
Comment # 8
on bug 8321
from Evan Huus
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #2)
> > > We may have to move the tapping point to just before calling
> > > dissect_rtp_data().
> >
> > Indeed the change seems to address this, although the solution has to be
> > verified.
>
> Looks like rtp_info is the only relevant part here, which isn't influenced
> by dissect_rtp_data(), so we should be fine.
>
> > In other news: this capture exposes an mp2t dissector bug. When adding a
> > zero length fragment to a composite the TVB asserts that.
>
> This is still a bug though.
GDB is giving me all sorts of weird internal errors when I try to debug this
but Valgrind doesn't show anything unusual. I'm not sure if my GDB is borked or
if there's something really subtle going on here.
I haven't even been able to determine if we're somehow getting a 0-length
fragment (so the assertion is from packet-mp2t.c:491) or if we're getting a
0-length subset to append (so the assertion is from packet-mp2t.c:494). GDB
doesn't want to let me step through any of the code in that area.
You are receiving this mail because:
- You are watching all bug changes.
