Other than these I think
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1531 should be
addressed as well, Although its consequences aren't fatal It looks
very ugly.
On 4/12/07, Anders Broman <a.broman@xxxxxxxxx> wrote:
Hi,
As Luis noted:
>Everyone that has touched the dfilter engine after the forking of
>0.99.5 (20465) must take a look at
>http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1521
because a nasty crash has being introduced since then.
My Windows build crashes as soon as I try to enter a filter L
>Someone that can actually understand the code in dissect_ber_choice() must
take a look at the attachments of:
>http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1342
>and
>http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
which I derived from it.
>I tried to find out what's going on.
In the bug report there is a ASN1 workaround but it would be nice to have a
better solution
>Last (in my list) there's Coverity's 216
>http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1326
>that might be the root cause of
>http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1429
>that's not that critical as an issue but having it working back would be
nice.
Must be solved first…
Best regards
Anders
________________________________
Från: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Kukosa,
Tomas
Skickat: den 12 april 2007 07:49
Till: Developer support list for Wireshark
Ämne: [Wireshark-dev] Next release?
Is there any timeframe for the next release?
T.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan