Re: [Wireshark-dev] Missing expert info

2010-12-19 Thread Christopher Maynard
Andreas writes: > So it looks like that it is bad practice to check for tree==NULL. The > proto_tree_add_... functions will check for tree==NULL by itself. The > delayed dissection was done for improved speed. ;-( Well, it's not bad practice per se, but it does require some careful considerati

Re: [Wireshark-dev] Missing expert info

2010-12-19 Thread Andreas
Am 10.12.2010 15:33, schrieb Christopher Maynard: > Andreas writes: > >> I found an inconsistency with the expert info. While expert infos of >> severity ERROR are reported, these are not displayed in the summary dialogs. > > Please file a bug report for this ... preferably with a capture file >

Re: [Wireshark-dev] Missing expert info

2010-12-10 Thread Christopher Maynard
Andreas writes: > I found an inconsistency with the expert info. While expert infos of > severity ERROR are reported, these are not displayed in the summary dialogs. Please file a bug report for this ... preferably with a capture file exhibiting the incorrect behavior attached to the report. T

[Wireshark-dev] Missing expert info

2010-12-10 Thread Andreas
Hi, I found an inconsistency with the expert info. While expert infos of severity ERROR are reported, these are not displayed in the summary dialogs. Symptoms: - lower-left corner of Wireshark-window shows a red balloon. - ballon-tip of this items shows: ERROR is the highest expert info