| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
remove C++ incompatibilities
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8416 attachment #10397
svn path=/trunk/; revision=48438
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[PATCH 1/2] Revert "Try to fix the "LNK4217: locally defined symbol"
warnings.
This reverts commit r48158.
[PATCH 2/2] Employ small hack in editcap to link with a few objects from
libwireshark properly
From me:
Add the ability to reset symbol exports via ws_symbol_export.h's include
guard and do so in capinfos.c and editcap.c. We include ws_symbol_export.h
in over 200 files so it didn't seem to make sense to remove its include
guard entirely.
svn path=/trunk/; revision=48170
|
|
|
|
| |
svn path=/trunk/; revision=48108
|
|
|
|
|
|
|
|
| |
is running" mutex. Have the NSIS installer check for this mutex and ask
the user to close Wireshark if it's found. While not perfect this makes
the WinSparkle update process much less annoying.
svn path=/trunk/; revision=47758
|
|
|
|
| |
svn path=/trunk/; revision=47065
|
|
|
|
|
|
|
| |
and as per email response from Richard Sharpe, add GPLv2+ boilerplate header
and license.
svn path=/trunk/; revision=47063
|
|
|
|
|
|
| |
Allow use of huges values for localtime / ctime / gmtime with MSVC 2008 or later
svn path=/trunk/; revision=46930
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cast away some implicit 64-bit-to-32-bit conversion errors due to use of
sizeof.
Cast away some implicit 64-bit-to-32-bit conversion errors due to use of
strtol() and strtoul().
Change some data types to avoid those implicit conversion warnings.
When assigning a constant to a float, make sure the constant isn't a
double, by appending "f" to the constant.
Constify a bunch of variables, parameters, and return values to
eliminate warnings due to strings being given const qualifiers. Cast
away those warnings in some cases where an API we don't control forces
us to do so.
Enable a bunch of additional warnings by default. Note why at least
some of the other warnings aren't enabled.
randpkt.c and text2pcap.c are used to build programs, so they don't need
to be in EXTRA_DIST.
If the user specifies --enable-warnings-as-errors, add -Werror *even if
the user specified --enable-extra-gcc-flags; assume they know what
they're doing and are willing to have the compile fail due to the extra
GCC warnings being treated as errors.
svn path=/trunk/; revision=46748
|
|
|
|
|
|
| |
Use pkthdr instead of pseudo_header as argument for dissecting.
svn path=/trunk/; revision=45601
|
|
|
|
|
|
|
|
| |
Have editcap use modulo when calculating filenum component of fileset name .
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7863
svn path=/trunk/; revision=45556
|
|
|
|
|
|
|
|
| |
Explicitly declare/cast 'unsigned <variable>' as 'unsigned int <variable>'
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7810
svn path=/trunk/; revision=45418
|
|
|
|
| |
svn path=/trunk/; revision=45015
|
|
|
|
|
|
| |
mismatches.
svn path=/trunk/; revision=44820
|
|
|
|
| |
svn path=/trunk/; revision=43738
|
|
|
|
|
|
|
|
| |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7350
By using wtap_dump_open_ng() in all places.
svn path=/trunk/; revision=43271
|
|
|
|
|
|
| |
fixes the double-free editcap crashes that the buildbot's been seeing lately.
svn path=/trunk/; revision=41542
|
|
|
|
|
|
|
|
| |
the shb_userappl value wasn't being changed.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6937
svn path=/trunk/; revision=41530
|
|
|
|
|
|
|
|
|
| |
to only add the name if no name if there yet. Original patch from
Jose Pedro Oliveira.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6937
svn path=/trunk/; revision=41524
|
|
|
|
| |
svn path=/trunk/; revision=41501
|
|
|
|
|
|
| |
files.
svn path=/trunk/; revision=41328
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using g_fprintf() fails (crashes) on Windows because the Windows GLib DLL
is linked with (depends upon) MSVCRT while editcap is linked with
(depends upon) MSVCR90.
IOW: "You can't do that ... (on Windows)"
See https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6695 (Comment 2)
for some additional information.
svn path=/trunk/; revision=41168
|
|
|
|
|
|
|
|
| |
Eliminate Mixture of libc and glibc in editcap.c
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6695
svn path=/trunk/; revision=40866
|
|
|
|
|
|
|
|
| |
help page update (pcapng is now the default file format).
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6551
svn path=/trunk/; revision=40658
|
|
|
|
| |
svn path=/trunk/; revision=40511
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
form of corruption/bogosity in a file, including in a file header as
well as in records in the file. Change the error message
wtap_strerror() returns for it to reflect that.
Use it for some file header problems for which it wasn't already being
used - WTAP_ERR_UNSUPPORTED shouldn't be used for that, it should only
be used for files that we have no reason to believe are invalid but that
have a version number we don't know about or some other
non-link-layer-encapsulation-type value we don't know about.
svn path=/trunk/; revision=40175
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
type" when writing out a capture file (i.e., writing a
per-packet-encapsulation capture to a file type that supports it but
doesn't support one of the packet's encapsulations), report the packet
number and, when doing this in a merge operation, report the file from
which it came.
When reporting "sorry, that file can't be written to a file of that
type, period", show the file type rather than the input file link-layer
type that causes the problem. (We could show both. We could be
*really* ambitious and iterate through all possible file types and show
the ones that will or at least might work....)
file_write_error_message() is documented as handling only UNIX-style
errnos, and libwireshark should be usable without libwiretap, so leave
it up to its callers to handle Wiretap errors such as
WTAP_ERR_SHORT_WRITE.
Clean up indentation.
svn path=/trunk/; revision=39949
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
getopt() can/should normally be found in unistd.h, so:
- When testing for getopt(), define that we HAVE_GETOPT instead of
HAVE_GETOPT_H (to avoid confusion).
- Don't attempt to include getopt.h: not all OS's have it (for example,
Solaris 9 does not).
- (All the places which need getopt already include unistd.h (if we have it).)
If this breaks things on some OS, we might need (a real) HAVE_GETOPT_H check.
svn path=/trunk/; revision=38437
|
|
|
|
|
|
| |
unnecessary.
svn path=/trunk/; revision=38155
|
|
|
|
| |
svn path=/trunk/; revision=38132
|
|
|
|
| |
svn path=/trunk/; revision=37768
|
|
|
|
|
|
|
|
| |
is mainly an attempt to fix the currently-broken "test.sh" step on the
XP buildbot. If this causes too many problems we might want to have
suite-capture.sh:capture_step_snapshot pass "-P" to dumpcap instead.
svn path=/trunk/; revision=37736
|
|
|
|
| |
svn path=/trunk/; revision=37669
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
check_startstop is set.
Refuse to write packets that do not fit in the file type we're writing. This
allows fuzz testing to be done on JPEGs without generating bogus files (with
packets bigger than the maximum packet size). This fixes
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6010 .
Note that this is only a problem with editcap is run with -T to force the
encapsulation type.
Maybe this needs a more generic solution (e.g., should this check be done in
the wiretap routines?), but at least for now it'll pacify the buildbot.
svn path=/trunk/; revision=37633
|
|
|
|
|
|
|
| |
than present, just chop all by setting caplen to 0. In all cases, don't touch
len. In other words, change incl_len but leave orig_len alone.
svn path=/trunk/; revision=37488
|
|
|
|
|
|
|
| |
original capture file's snaplen, save the new snaplen in the capture file
header so wireshark and capinfos can report it.
svn path=/trunk/; revision=37480
|
|
|
|
| |
svn path=/trunk/; revision=37372
|
|
|
|
| |
svn path=/trunk/; revision=36601
|
|
|
|
|
|
|
|
| |
`
Allow editcap to chop from beginning of packet for decapsulation
svn path=/trunk/; revision=35832
|
|
|
|
|
|
|
| |
UTF-8 where we don't already do so. In Wireshark use g_utf16_to_utf8
instead of utf_16to8. This should fix bug 5520.
svn path=/trunk/; revision=35411
|
|
|
|
| |
svn path=/trunk/; revision=35126
|
|
|
|
| |
svn path=/trunk/; revision=35024
|
|
|
|
| |
svn path=/trunk/; revision=35022
|
|
|
|
|
|
|
| |
Old behavior was to include a packet with a timestamp of 12:00:00.934 if -B "YYYY-MM-DD 12:00:00" was used.
svn path=/trunk/; revision=34913
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5353 :
editcap -h sends 9 lines to stderr and the rest to stdout. This problem
affects editcap 1.4.x (branch 1.4) and devel (trunk).
How to duplicate:
1) run "editcap -h"
2) run "editcap -h > /dev/null"
The attached patch replaces 9 ocurrences of "stderr" by "output" in the usage
function.
svn path=/trunk/; revision=34742
|
|
|
|
| |
svn path=/trunk/; revision=34137
|
|
|
|
| |
svn path=/trunk/; revision=33077
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a new '-S' option to editcap that will rewrite timestamps of
packets to insure that the new capture file is in strict chronological order.
This option's primary use case is to fixup the occasional timestamps that have
a negative delta time relative to previous packet.
This feature is related to (but does not depend on) capinfos enhancement
submitted in bug #4315 which helps identify tracefiles with "out-of-order"
packets.
svn path=/trunk/; revision=33042
|
|
|
|
| |
svn path=/trunk/; revision=33012
|
|
|
|
| |
svn path=/trunk/; revision=31729
|
|
|
|
|
|
|
|
| |
send normal -h output to stdout so it can be paginated and the usage output
to stderr when there was an error in the command arguments.
svn path=/trunk/; revision=31388
|