Wireshark-bugs: [Wireshark-bugs] [Bug 9129] Crash then try to delete the same entry (length rang
Martin Kaiser
changed
bug 9129
What |
Removed |
Added |
CC |
|
wireshark@kaiser.cx
|
Comment # 1
on bug 9129
from Martin Kaiser
Hi,
thanks for reporting this. I could reproduce it rather easily.
Each deletion works based on the index of the entry in the list. You can bring
up multiple confirmation popups.
If the related index does not longer exist when you confirm the deletion, we
hit the assert in uat_remove_record_idx(). If the index now points to some
other data (say you originally seleted index 2 for deletion and index 1 was
deleted while your confirm dialogue is up and 2->1, 3->2, ...), you'll delete a
different entry than you originally selected :-(
I'd guess there's no point in having more than one pending "confirm deletion"
popup at a time. I'll attach a patch to do this and leave it up to others to
comment in case I missed something.
We might run into the same problem with combinations of Edit and Delete popups,
probably they should be mutually exclusive as well.
And I was wondering if we're going to see the same issue in the Qt version...
You are receiving this mail because:
- You are watching all bug changes.