Age | Commit message (Collapse) | Author | Files | Lines |
|
svn path=/trunk/; revision=37123
|
|
http://www.wireshark.org/lists/wireshark-dev/200910/msg00074.html
g_slice allocing the keys should make it possible to walk the
fragment table and free the fragments once they are g_slice_alloced.
It remains fo figure out how to do that.
svn path=/trunk/; revision=37112
|
|
svn path=/trunk/; revision=36223
|
|
current fragment pushes us past the reassembled size: it may be that the
current fragment is a duplicate/retransmission and will be ignored.
Also, if we detect a conflict between a previous and the current fragment,
flag the current (conflicting) fragment as FD_OVERLAPCONFLICT. Do *not* flag
the fragment that got us into the reassembly routine (probably the final
fragment): it is not (may not be) the guilty fragment.
Clean up some spacing.
Also add reassembly tests for duplicate/retransmitted fragments.
svn path=/trunk/; revision=36131
|
|
svn path=/trunk/; revision=36002
|
|
svn path=/trunk/; revision=35705
|
|
svn path=/trunk/; revision=35176
|
|
Essentially: doing g_slice_free with the wrong 'type' for the data to be freed.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5477
svn path=/trunk/; revision=35175
|
|
reassemble.c:220: warning: unused parameter 'key_arg'
svn path=/trunk/; revision=35156
|
|
reassemble.c:222: warning: unused variable 'key'
svn path=/trunk/; revision=35155
|
|
svn path=/trunk/; revision=35154
|
|
Free fragment data and fragment keys in fragment_table when neccessary. reassembled_table remains to be fixed.
svn path=/trunk/; revision=35153
|
|
the data source does not need to be allocated if (!tree).
Rev 30158 took the if (!tree) check out indicating that the check was invalid.
So: (since packet_add_new_data_source() now only calls add_new_data_source()),
remove packet_add_new_data_source().
svn path=/trunk/; revision=34717
|
|
one fragment to reassemble.
svn path=/trunk/; revision=34285
|
|
conflict when they are named fragments instead of segments and to avoid
duplicating the fragments/segments text.
svn path=/trunk/; revision=34074
|
|
Show number of segments which were used in the desgementation.
svn path=/trunk/; revision=34072
|
|
compiling again.
fragment_add_seq_check(), fragment_add_seq_802_11(), and fragment_add_seq_next()
all call fragment_add_seq_check_work() so make their prototypes match each other
in const-ness. This fixes a warning when compiling reassemble_test.
svn path=/trunk/; revision=32933
|
|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4422
From me: Fix a number of instances where the function prototype or
the function definition wasn't changed so there was a mismatch
thus causing Windows (but not gcc) compilation errors.
svn path=/trunk/; revision=32365
|
|
svn path=/trunk/; revision=32361
|
|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4422
svn path=/trunk/; revision=32360
|
|
reassembly.
svn path=/trunk/; revision=31767
|
|
buildbot test failures.
svn path=/trunk/; revision=30639
|
|
svn path=/trunk/; revision=30621
|
|
svn path=/trunk/; revision=30607
|
|
- it contains pointers to a couple malloc()'d addresses
- it is inserted in the fragment table (the contents of which are
g_free()'d in free_all_fragments())
Instead, do like fragment_key_copy() and use a g_slice or g_chunk, depending
on the glib version.
svn path=/trunk/; revision=30599
|
|
free memory properly on shutdown.
This is an initial step. There's still some work to do.
svn path=/trunk/; revision=29754
|
|
svn path=/trunk/; revision=29446
|
|
svn path=/trunk/; revision=29440
|
|
deprecates add_new_data_source(). This is based on the following observation:
1) The tvb + name (aka. data_source) is only used when the protocol tree is visible
The current implementation of add_new_data_source() doesn't take this into account and simply allocates a data_source regardless. This is what packet_add_new_data_source() tries to rectify.
A couple of dissectors have already been switched over to the new packet_add_new_data_source(). Many are still missing. Help appreciated!
svn path=/trunk/; revision=29427
|
|
svn path=/trunk/; revision=29397
|
|
svn path=/trunk/; revision=29205
|
|
svn path=/trunk/; revision=29128
|
|
g_free() is NULL safe, so we don't need check against it.
svn path=/trunk/; revision=27718
|
|
svn path=/trunk/; revision=25345
|
|
svn path=/trunk/; revision=25343
|
|
svn path=/trunk/; revision=25253
|
|
Use O(1) logic for the fast path when adding fragments (ie fragments are in order).
svn path=/trunk/; revision=23422
|
|
svn path=/trunk/; revision=22513
|
|
fragmented data without adding an empty data fragment.
This is used by the RTSE dissector which can't identify the
last fragment until after it has been added.
svn path=/trunk/; revision=22174
|
|
under gcc to tools/lemon, plugins/mate and epan/
svn path=/trunk/; revision=21204
|
|
01_reassemble_test.patch
------------------------
I didn't want to do anything without some unit tests, so here they are.
This allows a standalone binary, epan/reassemble_test, to be built; this can be run from the commandline and should end up printing out "success"
if all goes well.
NOTE the changes to makefile.am NOT checked in currently.
Incidentally: is it possible to get the buildbot to run things like this, exntest and tvbtest?
02_reassemble_refactor.patch
----------------------------
fragment_add_seq, fragment_add_dcerpc_dg and fragment_add_seq_check_work were all pretty much carbon-copies of each other. This patch factors out the common parts of the routines into a new routine, fragment_add_seq_key().
03_reassemble_partial_reassembly.patch
---------------------------------------
This makes fragment_set_partial_reassembly() work for datagrams assembled with fragment_add_seq(). The patch itself is actually quite small, but it adds another unit test which is reasonably lengthy.
svn path=/trunk/; revision=20888
|
|
svn path=/trunk/; revision=20863
|
|
having been reassembled.
Fix the comments in reassembly.c and reassembly.h regarding what the reassembly
routines actually return in the 802.11 and no-sequence-number cases when they
are given the first and last packet (that is, a non-segmented packet): in
particular the routines return a pointer to a list containing just the one
fragment.
svn path=/trunk/; revision=20505
|
|
Clean up indentation.
svn path=/trunk/; revision=19953
|
|
svn path=/trunk/; revision=18197
|
|
commit
svn path=/trunk/; revision=17074
|
|
number (experimental)
add a check to fragment_add_common() if the given tvb parameters are ok, otherwise throw a DissectorError
add some more symbols to libethereal.def
svn path=/trunk/; revision=17073
|
|
Find attached a couple of changes for t38:
- Use the dissector to reassemble t30 frames
- Dissect t30 protocol
- Move the "Fax t38 analysis" to the "VoIP Calls". Now when selecting
"Statistics"->"Fax t38 analysis" option, there is a message that
redirect the user to use the "Voip calls" instead. We may keep this
option for one release, and then remove it ?
- Added in the "Voip calls" the ability to detect a t38 call if there
are not signaling associated with it. For example, when using "Decode
as.." to dissect t38 packets, it is possible to use the "Voip calls" to analyze that call.
- Display "SDP (t38)" in the "Voip calls graph" for SDP t38 sessions.
Regards
Alejandro Vaquero
svn path=/trunk/; revision=17033
|
|
reassemble.c about the handling of zero-length fragments.
svn path=/trunk/; revision=15899
|
|
fragment_add_seq_next() function instead of fragment_add()
in addition, I had to implement fragment_get_reassembled() in addition to fragment_get(), which works with reassembled_table
svn path=/trunk/; revision=15762
|