This bug was fixed in the package sniffit - 0.3.7.beta-13ubuntu1
---
sniffit (0.3.7.beta-13ubuntu1) karmic; urgency=low
[ Karoly Segesdi ]
* #include more headers, so that prototyes are correctly defined, avoiding
some crashes. (LP: #107180)
-- James Westby
This bug is caused by implicit declarations of functions coming from
string.h, which in turn is caused by missing #include statements. I have
fixed all implicit declarations by providing the neccessary #include
statements. Please see attached patch agains 0.3.7.beta-13.
Hope this helps.
**
** Changed in: sniffit (Ubuntu)
Status: Invalid = Confirmed
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug still exists in Ubuntu 9.04 64-bit.
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
No progress on this bug, and so I'm marking it as invalid.
** Changed in: sniffit (Ubuntu)
Status: Confirmed = Invalid
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
It sounds like this is an application bug, so reassigning back there. I
suggest using the valgrind tool to pinpoint the location of the problem
more precisely.
** Changed in: sniffit (Ubuntu)
Sourcepackagename: linux-source-2.6.20 = sniffit
--
Segmentation Fault
(Seriously, it really is very likely that this is an application bug.
For example, one of the variables involved being the wrong type or
strtok() being declared with the wrong prototype or something like that
would easily cause this kind of thing. While it's not impossible that
the libc or gcc is
From the susv3 manual:
char *strtok(char *restrict s1, const char *restrict s2);
The first call in the sequence searches the string pointed to by s1 for
the first byte that is not contained in the current separator string
pointed to by s2. If no such byte is found, then there are no tokens in
Hi Jeff,
thanks for helping.
I have seen similar manual pages, and also the GNU one (for instance
http://www.gnu.org/software/libc/manual/html_node/Finding-Tokens-in-a-String.html).
If you read yours carefully, it said that if there is no byte is s1 which is
not in s2 than it returns NULL.
I've
Just to make things clearer (I hope), I modified the snippet above
as follows:
strncpy(hlp,optarg,299);
printf(hlp :%x-\n, hlp);
printf(hlp :%s-\n, hlp);
hlp2=strtok(hlp,:);
printf(hlp :%x-\n, hlp);
printf(hlp :%s-\n, hlp);
The kernel mem subsystem and glibc are extremely well tested, it is
highly unlikely these are the cause of the problems. User level app
bugs are by far the most likely explanation.
If hlp and hlp2 point to the same memory, they should behave the same
when accessed. Unfortunately, the above
Thanks Phillip!
I think we are getting somewhere. Here is the modified snippet:
hlp[299]=0;
strncpy(hlp,optarg,299);
printf(hlp :%p-\n, hlp);
printf(hlp :%s-\n, hlp);
hlp2=strtok(hlp,:);
printf(hlp :%p-\n, hlp);
printf(hlp
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: gcc-4.1 = linux-source-2.6.20
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gcc-4.1 (Ubuntu)
Sourcepackagename: linux-source-2.6.20 = gcc-4.1
Status: Needs Info = Confirmed
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Oh my my, do I write like a coyote or what? I meant bits not bytes in previous
post.
Just a wild guess here, but is it so impossible that there is a bug in the
segmentation code?
Any idea how to debug this further?
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received
Log
** Attachment added: Crash log
http://librarian.launchpad.net/7338919/_usr_sbin_sniffit.1000.crash
--
Segmentation Fault
https://bugs.launchpad.net/bugs/107180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Alessio,
one of the calls to the library strncpy() function in sniffit contains
illegal data (which results in a the application trying to access a memory
location outside of its address space).
My guess is that this is the one in sn_analyse.c
You should recompile sniffit with debug support and
After some more investigations I believe there could be a problem with
the C library strtok() function.
the outpur of strtok(62.94.1.193, : ) should be 62.94.1.193; it
is however NULL
I also tried the reentrant strsep() but with similar results.
I'm still investigating.
** Changed in: glibc
I'm wondering if this could be a memory management/kernel issue or perhaps a
gcc one.
Here is a snippet of the code which is causing the SIGSEG (there are other
similar ones):
char hlp[300], *hlp2;
hlp[299]=0;
strncpy(hlp,optarg,299);
hlp2=(char *)strtok(hlp,:);
IP[255]=0;
19 matches
Mail list logo
