Comment # 6
on bug 10233
from Bill Meier
(In reply to Hadriel Kaplan from comment #4)
> libgtk continuing and calling gtk_tree_view_column_cell_set_cell_data(),
> followed by wireshark calling packet_list_get_value(), then
> packet_list_dissect_and_cache_record(), then epan_dissect_run() and finally
> wmem_enter_packet_scope().
Yep: sounds like queued-up gtk callbacks are being executed when
gtk_dialog_run() is executed (as part of doing the alert box) since that
effectively runs gtk_main_loop().
There's lots of "interrupt" (callback) type stuff related to updating the
packet display going on with the our packet_list widget which I've never fully
grasped.
There may be a way to still use report_failure() in the middle of doing a
dissection and not get thrown into the swamp, but I don't know how.
When the internal error occurs, is it possible to just put an error entry onto
the dissection tree (using expert... or whatever) ? (I haven't actually looked
at the code).
Bill
You are receiving this mail because:
- You are watching all bug changes.