Re: [Wireshark-dev] cleanup_dissection() called both on cf_close and cf_open()

2013-03-25 Thread Evan Huus
On Mon, Mar 25, 2013 at 3:37 PM, Gerald Combs wrote: > On 3/24/13 7:37 AM, Anders Broman wrote: >> Hi, >> Looking into address resolution I found that the hosts file is read >> multiple times partly >> because it's part of cleanup_dissection() which is called both on >> cf_open() and cf_close(). >

Re: [Wireshark-dev] cleanup_dissection() called both on cf_close and cf_open()

2013-03-25 Thread Gerald Combs
On 3/24/13 7:37 AM, Anders Broman wrote: > Hi, > Looking into address resolution I found that the hosts file is read > multiple times partly > because it's part of cleanup_dissection() which is called both on > cf_open() and cf_close(). > > Should cleanup_dissection() take an argument showing whet

Re: [Wireshark-dev] cleanup_dissection() called both on cf_close and cf_open()

2013-03-24 Thread Evan Huus
On Sun, Mar 24, 2013 at 10:37 AM, Anders Broman wrote: > Hi, > Looking into address resolution I found that the hosts file is read multiple > times partly > because it's part of cleanup_dissection() which is called both on cf_open() > and cf_close(). > > Should cleanup_dissection() take an argumen

[Wireshark-dev] cleanup_dissection() called both on cf_close and cf_open()

2013-03-24 Thread Anders Broman
Hi, Looking into address resolution I found that the hosts file is read multiple times partly because it's part of cleanup_dissection() which is called both on cf_open() and cf_close(). Should cleanup_dissection() take an argument showing whether its a file open or file close operation and di