File: KNOWN-BUGS.texinfo

package info (click to toggle)
tcpick 0.2.1-6
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd, squeeze, wheezy
  • size: 876 kB
  • ctags: 624
  • sloc: ansic: 2,506; sh: 931; makefile: 61
file content (102 lines) | stat: -rw-r--r-- 2,256 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
\input texinfo  @c -*-texinfo-*-
@setfilename KNOWN-BUGS
@settitle KNOWN-BUGS

@c @setchapternewpage odd
@c @paragraphindent asis

@c 1st page:
@titlepage
@title KNOWN-BUGS
@subtitle Known Bugs of the Tcpick sniffer
@author Francesco 'duskdruid' Stablum

@c copyright page
@end titlepage
@headings single

@c Contenuti
@contents

@c capitolo primo

@itemize

@item

Kirash reported under BSD: 

read() called by pcap_read() called by pcap_loop() blocks the program
until gets about 600.000 byte and then calls got_packet(). Then it
blocks until other 600.000 bytes aren't captured.
It may be a problem of setitimer. If setitimer is set to 2 seconds,
the program works fine, but this is only a workaround.

This seem to be a kernel bug:

Subject: kern/26470: all process stop for a long time by calling
settimeofday() and setitimer()

List: netbsd-bugs

Date: 07/29/2004 04:32:58

[cut]

Description:

All process stops for a long time by calling setitimer() with short
interval and then putting the system clock forward long. 

This bug has been workarounded with a fork + sleep + kill trick.

@item

Segmentation fault in status_switch(): prev->next is null.
I cannot understand this, because the malloc *didn't return NULL*, but a
valid address as gdb said me!. WTF!
NOTE: this is a very rare bug.

@item

Marcos Costantini reported a segmentation fault bug in tcpick running on a
MacOSX system.

@item
Penelope Fudd wrote:

Hi..

I've got a tcpdump program running that logs all email to & from the
mail server.

When I use 'tcpick -wR -r log-2004.xx.xx', and look at the resulting
client and server files, there are binary strings stuck in the middle
of
the conversation:

[cut]

Where are these 'A0 00 00 00 00 00' chunks coming from?  I thought
that -wR was binary-safe.  When I follow the stream using Ethereal, the
problem goes away.

@item

maybe it doesn't go in promisc mode even without -p

@end itemize

@unnumbered Patches

We need somebody suggesting bugs and new features!

If you want to give some help, please subscribe to the mailing-list:

<tcpick-project @ lists.sourceforge.net>

Archive: http://sourceforge.net/mailarchive/forum.php?forum=tcpick-project

Subscribe: http://lists.sourceforge.net/lists/listinfo/tcpick-project

thanks