[Buildroot] segmentation fault running kismet

[Buildroot] segmentation fault running kismet

[Saurav Kumar Barik]

Hi,



I am getting segmentation fault with kismet.

My setup is -

Gateworks BSP 0.7

Buildroot

Linux-2.6.21.4

kismet-2007-10-R1



I followed the following thread for integrating kismet -

*	http://www.busybox.net/lists/buildroot/2007-October/006129.html

There were no issues with the build. I cross verified the kismet.conf
file and the values were proper.



************************************************************************
**********************

[root at saurav]# ./kismet_server -f kismet.conf

Using alternate config file: kismet.conf

Will drop privs to saurav (1001) gid 1001

No specific sources given to be enabled, all will be enabled.

Enabling channel hopping.

Enabling channel splitting.

Dropped privs to saurav (1001) gid 1001

WARNING:  Disabling GPS logging.

Logging networks to Kismet.network

Logging networks in CSV format to Kismet.csv

Logging networks in XML format to Kismet.xml

Logging cryptographically weak packets to Kismet.weak

Logging cisco product information to Kismet.cisco

Tracking probe responses and associating probe networks.

Reading AP manufacturer data and defaults from /home/saurav/ap_manuf

Reading client manufacturer data and defaults from
/home/saurav/client_manuf

Segmentation fault

************************************************************************
***********************



Has anybody successfully used kismet with buildroot?

I shall be grateful if somebody could share some pointers on this issue.



Thanks & Regards,

Saurav





This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no  liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.

www.aztecsoft.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080207/949208dd/attachment.htm 

[Buildroot] segmentation fault running kismet

[Joe]

Do you really want an answer? So get rid of this. Some other MLs would 
have you banned on the spot.

> This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no  liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
> The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.

Greetz Joe

-- 
Sepp "ZaP" Holzmayr

please reply to: zentrale.at.work at gmail.com
"Never underestimate the bandwidth of a freight train full of DAT tapes. 
Only the round-trip is a little suboptimal."

[Buildroot] segmentation fault running kismet

[Yogesh Kumar Sharma]

Joe et al.,
Please help him and ignore the disclaimer.
Neither Saurav nor I can help remove it from the mailer.

And to top it, we don't have permission to access to external
(un-official) mail servers; therefore we cannot help but send
mails/requests from official id.

Sorry for the inconvenience caused.

Thanks & Regards,
yogesh


-----Original Message-----
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org]
On Behalf Of Joe
Sent: Thursday, February 07, 2008 10:46 PM
To: Saurav Kumar Barik
Cc: buildroot at uclibc.org
Subject: Re: [Buildroot] segmentation fault running kismet


Do you really want an answer? So get rid of this. Some other MLs would
have you banned on the spot.

> This email message and its attachments may contain CONFIDENTIAL AND
> PRIVILEGED INFORMATION intended for the sole use of the addressee(s).
> If you have received it in error, please contact the sender by return
> email, notify your system manager and destroy the original message and

> any copies thereof. Any review, use, disclosure or distribution is
> unlawful. Please check this email and any attachments for the presence

> of viruses. The Company accepts no  liability for any damage caused by

> any virus transmitted by this email. The views or opinions presented
> in this e-mail are solely those of the author and do not necessarily
> represent those of the company. The Company reserves the right to
> monitor, review and store the content of all messages sent to or from
> this e-mail address.

Greetz Joe

--
Sepp "ZaP" Holzmayr

please reply to: zentrale.at.work at gmail.com
"Never underestimate the bandwidth of a freight train full of DAT tapes.

Only the round-trip is a little suboptimal."
_______________________________________________
buildroot mailing list
buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot

This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no  liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.

www.aztecsoft.com

[Buildroot] segmentation fault running kismet

[saurav barik]

 Hi,

I am getting segmentation fault with kismet.

My setup is .
Gateworks BSP 0.7
Buildroot
Linux-2.6.21.4
kismet-2007-10-R1

I followed the following thread for integrating kismet .
    http://www.busybox.net/lists/buildroot/2007-October/006129.html
There were no issues with the build. I cross verified the kismet.conf
file and the values were proper.

**********************************************************************************************
[root at saurav]# ./kismet_server -f kismet.conf
Using alternate config file: kismet.conf
Will drop privs to saurav (1001) gid 1001
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Dropped privs to saurav (1001) gid 1001
WARNING:  Disabling GPS logging.
Logging networks to Kismet.network
Logging networks in CSV format to Kismet.csv
Logging networks in XML format to Kismet.xml
Logging cryptographically weak packets to Kismet.weak
Logging cisco product information to Kismet.cisco
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /home/saurav/ap_manuf
Reading client manufacturer data and defaults from /home/saurav/client_manuf

Segmentation fault
***********************************************************************************************

Has anybody successfully used kismet with buildroot?
I shall be grateful if somebody could share some pointers on this issue.

Thanks & Regards,
Saurav

PS: I earlier sent same mail from my company's mail id, but since that
mail had company's disclaimer towards the end of it; therefore am
sending it again from a personal mail id. Thanks Joe for pointing that
out. Please help :-).

[Buildroot] segmentation fault running kismet

[Ulf Samuelsson]

> 
> Joe et al.,
> Please help him and ignore the disclaimer.
> Neither Saurav nor I can help remove it from the mailer.
> 
> And to top it, we don't have permission to access to external
> (un-official) mail servers; therefore we cannot help but send
> mails/requests from official id.
> 
> Sorry for the inconvenience caused.
> 
> Thanks & Regards,
> yogesh
> 

The mailing list IS disclosing and distributing the mail.
You can add a disclaimer in your signature
saying that the comment below is not applicable to
any mail sent to an public mailing list!
Otherwise you should not be sending mails to mailing lists.

Best Regards
Ulf Samuelsson


> 
> -----Original Message-----
> From: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org]
> On Behalf Of Joe
> Sent: Thursday, February 07, 2008 10:46 PM
> To: Saurav Kumar Barik
> Cc: buildroot at uclibc.org
> Subject: Re: [Buildroot] segmentation fault running kismet
> 
> 
> Do you really want an answer? So get rid of this. Some other MLs would
> have you banned on the spot.
> 
>> This email message and its attachments may contain CONFIDENTIAL AND
>> PRIVILEGED INFORMATION intended for the sole use of the addressee(s).
>> If you have received it in error, please contact the sender by return
>> email, notify your system manager and destroy the original message and
> 
>> any copies thereof. Any review, use, disclosure or distribution is
>> unlawful. Please check this email and any attachments for the presence
> 
>> of viruses. The Company accepts no  liability for any damage caused by
> 
>> any virus transmitted by this email. The views or opinions presented
>> in this e-mail are solely those of the author and do not necessarily
>> represent those of the company. The Company reserves the right to
>> monitor, review and store the content of all messages sent to or from
>> this e-mail address.
> 
> Greetz Joe
> 
> --
> Sepp "ZaP" Holzmayr
> 
> please reply to: zentrale.at.work at gmail.com
> "Never underestimate the bandwidth of a freight train full of DAT tapes.
> 
> Only the round-trip is a little suboptimal."
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot
> 
> This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no  liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
> The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.
> 
> www.aztecsoft.com
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>

[Buildroot] segmentation fault running kismet

[Joe]

GMail is fine, i see :-)

saurav barik schrieb:
> My setup is .
> Gateworks BSP 0.7
> Buildroot
> Linux-2.6.21.4
> kismet-2007-10-R1

You might also want to name your architecture, for it is also relevant 
for memory issues.
I'm not a kismet user myself, but i've had a lot of segfault trouble 
when experimenting with EABI an my ARM platform.

Greetz Joe
-- 
Sepp "ZaP" Holzmayr

please reply to: zentrale.at.work at gmail.com
"Never underestimate the bandwidth of a freight train full of DAT tapes. 
Only the round-trip is a little suboptimal."

[Buildroot] segmentation fault running kismet

[saurav barik]

On 2/8/08, Joe <zentrale.at.work@gmail.com> wrote:
> GMail is fine, i see :-)
>
> saurav barik schrieb:
> > My setup is .
> > Gateworks BSP 0.7
> > Buildroot
> > Linux-2.6.21.4
> > kismet-2007-10-R1
>
> You might also want to name your architecture, for it is also relevant
> for memory issues.
> I'm not a kismet user myself, but i've had a lot of segfault trouble
> when experimenting with EABI an my ARM platform.
>
> Greetz Joe

I am using Gateworks  GW2348 on my IXP board. My architecture is
armv5teb. The target ABI is set to OABI.
I ran gdb on the kimset_server and have copied some of the relevant
info below. It seems it crashes in the C++ STL libraries.

Thanks & Regards,
Saurav

*******************************************************************
GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "armeb-linux-uclibc"...
(gdb)
(gdb) r
Starting program: /mnt/kismet_2007/kismet_server
Will drop privs to saurav (1001) gid 1001
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Dropped privs to saurav (1001) gid 1001
WARNING:  Disabling GPS logging.
Logging networks to Kismet.network
Logging networks in CSV format to Kismet.csv
Logging networks in XML format to Kismet.xml
Logging cryptographically weak packets to Kismet.weak
Logging cisco product information to Kismet.cisco
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /home/saurav/ap_manuf
Reading client manufacturer data and defaults from /home/saurav/client_manuf

Program received signal SIGSEGV, Segmentation fault.
0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
    in_types=@0xbef08dac, in_parm=<value optimized out>)
    at packetsourcetracker.cc:759
759	packetsourcetracker.cc: No such file or directory.
	in packetsourcetracker.cc


(gdb) bt
#0  0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
    in_types=@0xbef08dac, in_parm=<value optimized out>)
    at packetsourcetracker.cc:759
#1  0x0008b428 in ProcessBulkConf (conf=Cannot access memory at
address 0xffffff38
) at kismet_server.cc:2098
#2  0x000a76ac in main (argc=-335704437, argv=0xcc814) at kismet_server.cc:2650


(gdb) info frame 0
Stack frame at 0xbef06f54:
 pc = 0x35be8 in Packetsourcetracker::SetTypeParms(std::string, packet_parm)
    (packetsourcetracker.cc:759); saved pc 0x8b428
 called by frame at 0xbef09458
 source language c++.
 Arglist at 0xbef06f50, args: this=0xeb07c, in_types=@0xbef08dac,
    in_parm=<value optimized out>
 Locals at 0xbef06f50, Previous frame's sp at 0xbef06f48
 Saved registers:
  r4 at 0xbef06f28, r5 at 0xbef06f2c, r6 at 0xbef06f30, r7 at 0xbef06f34,
  r8 at 0xbef06f38, r9 at 0xbef06f3c, r10 at 0xbef06f40, r11 at 0xbef06f44,
  lr at 0xbef06f4c, pc at 0xbef06f4c, f4 at 0xbef06ef8, f5 at 0xbef06f04,
  f6 at 0xbef06f10, f7 at 0xbef06f1c

(gdb) info frame 1
Stack frame at 0xbef09458:
 pc = 0x8b428 in ProcessBulkConf(ConfigFile*) (kismet_server.cc:2098);
    saved pc 0xa76ac
 called by frame at 0xbef0faf0, caller of frame at 0xbef06f54
 source language c++.
 Arglist at 0xbef09454, args: conf=Cannot access memory at address 0xffffff38


(gdb) info frame 2
Stack frame at 0xbef0faf0:
 pc = 0xa76ac in main (kismet_server.cc:2650); saved pc 0x4014b380
 caller of frame at 0xbef09458
 source language c++.
 Arglist at 0xbef0faec, args: argc=-335704437, argv=0xcc814
 Locals at 0xbef0faec, Previous frame's sp at 0xbef0fae4
 Saved registers:
  r4 at 0xbef0fac4, r5 at 0xbef0fac8, r6 at 0xbef0facc, r7 at 0xbef0fad0,
  r8 at 0xbef0fad4, r9 at 0xbef0fad8, r10 at 0xbef0fadc, r11 at 0xbef0fae0,
  lr at 0xbef0fae8, pc at 0xbef0fae8, f4 at 0xbef0fa94, f5 at 0xbef0faa0,
  f6 at 0xbef0faac, f7 at 0xbef0fab8


(gdb)
(gdb) bt
#0  0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
    in_types=@0xbef08dac, in_parm=<value optimized out>)
    at packetsourcetracker.cc:759
#1  0x0008b428 in ProcessBulkConf (conf=Cannot access memory at
address 0xffffff38
) at kismet_server.cc:2098
#2  0x000a76ac in main (argc=-335704437, argv=0xcc814) at kismet_server.cc:2650
**************************************************************************

[Buildroot] segmentation fault running kismet

[saurav barik]

The strange thing I noticed is that if I run the help menu then also I
get segmentation fault. I am not sure where things are going wrong.
Anybody using Kismet-2007-10-R1 with buildroot?
Please let me know.

Thanks & Regards,
Saurav

********************************************************************
[root at saurav mnt]# ./kismet_server --help
Usage: ./kismet_server [OPTION]
Most (or all) of these options can (and should) be configured via the
kismet.conf global config file, but can be overridden here.
  -I, --initial-channel <n:c>  Initial channel to monitor on (default: 6)
                                Format capname:channel
  -x, --force-channel-hop      Forcibly enable the channel hopper
  -X, --force-no-channel-hop   Forcibly disable the channel hopper
  -t, --log-title <title>      Custom log file title
  -n, --no-logging             No logging (only process packets)
  -f, --config-file <file>     Use alternate config file
  -c, --capture-source <src>   Packet capture source line (type,interface,name)
  -C, --enable-capture-sources Comma separated list of named packet
sources to use.
  -l, --log-types <types>      Comma separated list of types to log,
                                (ie, dump,cisco,weak,network,gps)
  -d, --dump-type <type>       Dumpfile type (wiretap)
  -m, --max-packets <num>      Maximum number of packets before
starting new dump
  -q, --quiet                  Don't play sounds
  -g, --gps <host:port>        GPS server (host:port or off)
  -p, --port <port>            TCPIP server port for GUI connections
  -a, --allowed-hosts <hosts>  Comma separated list of hosts allowed to connect
  -b, --bind-address <address>    Bind to this address. Default INADDR_ANY
  -r, --retain-monitor         Leave card in monitor mode on exit
  -s, --silent                 Don't send any output to console.
  -N, --server-name            Server name
      --daemonize              Background server in daemon mode
  -v, --version                Kismet version
  -h, --help                   What do you think you're reading?
Segmentation fault
[root at saurav mnt]#
**************************************************************************


On 2/8/08, saurav barik <saurav.barik@gmail.com> wrote:
> On 2/8/08, Joe <zentrale.at.work@gmail.com> wrote:
> > GMail is fine, i see :-)
> >
> > saurav barik schrieb:
> > > My setup is .
> > > Gateworks BSP 0.7
> > > Buildroot
> > > Linux-2.6.21.4
> > > kismet-2007-10-R1
> >
> > You might also want to name your architecture, for it is also relevant
> > for memory issues.
> > I'm not a kismet user myself, but i've had a lot of segfault trouble
> > when experimenting with EABI an my ARM platform.
> >
> > Greetz Joe
>
> I am using Gateworks  GW2348 on my IXP board. My architecture is
> armv5teb. The target ABI is set to OABI.
> I ran gdb on the kimset_server and have copied some of the relevant
> info below. It seems it crashes in the C++ STL libraries.
>
> Thanks & Regards,
> Saurav
>
> *******************************************************************
> GNU gdb 6.7.1
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "armeb-linux-uclibc"...
> (gdb)
> (gdb) r
> Starting program: /mnt/kismet_2007/kismet_server
> Will drop privs to saurav (1001) gid 1001
> No specific sources given to be enabled, all will be enabled.
> Enabling channel hopping.
> Enabling channel splitting.
> Dropped privs to saurav (1001) gid 1001
> WARNING:  Disabling GPS logging.
> Logging networks to Kismet.network
> Logging networks in CSV format to Kismet.csv
> Logging networks in XML format to Kismet.xml
> Logging cryptographically weak packets to Kismet.weak
> Logging cisco product information to Kismet.cisco
> Tracking probe responses and associating probe networks.
> Reading AP manufacturer data and defaults from /home/saurav/ap_manuf
> Reading client manufacturer data and defaults from /home/saurav/client_manuf
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
>     in_types=@0xbef08dac, in_parm=<value optimized out>)
>     at packetsourcetracker.cc:759
> 759	packetsourcetracker.cc: No such file or directory.
> 	in packetsourcetracker.cc
>
>
> (gdb) bt
> #0  0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
>     in_types=@0xbef08dac, in_parm=<value optimized out>)
>     at packetsourcetracker.cc:759
> #1  0x0008b428 in ProcessBulkConf (conf=Cannot access memory at
> address 0xffffff38
> ) at kismet_server.cc:2098
> #2  0x000a76ac in main (argc=-335704437, argv=0xcc814) at
> kismet_server.cc:2650
>
>
> (gdb) info frame 0
> Stack frame at 0xbef06f54:
>  pc = 0x35be8 in Packetsourcetracker::SetTypeParms(std::string, packet_parm)
>     (packetsourcetracker.cc:759); saved pc 0x8b428
>  called by frame at 0xbef09458
>  source language c++.
>  Arglist at 0xbef06f50, args: this=0xeb07c, in_types=@0xbef08dac,
>     in_parm=<value optimized out>
>  Locals at 0xbef06f50, Previous frame's sp at 0xbef06f48
>  Saved registers:
>   r4 at 0xbef06f28, r5 at 0xbef06f2c, r6 at 0xbef06f30, r7 at 0xbef06f34,
>   r8 at 0xbef06f38, r9 at 0xbef06f3c, r10 at 0xbef06f40, r11 at 0xbef06f44,
>   lr at 0xbef06f4c, pc at 0xbef06f4c, f4 at 0xbef06ef8, f5 at 0xbef06f04,
>   f6 at 0xbef06f10, f7 at 0xbef06f1c
>
> (gdb) info frame 1
> Stack frame at 0xbef09458:
>  pc = 0x8b428 in ProcessBulkConf(ConfigFile*) (kismet_server.cc:2098);
>     saved pc 0xa76ac
>  called by frame at 0xbef0faf0, caller of frame at 0xbef06f54
>  source language c++.
>  Arglist at 0xbef09454, args: conf=Cannot access memory at address
> 0xffffff38
>
>
> (gdb) info frame 2
> Stack frame at 0xbef0faf0:
>  pc = 0xa76ac in main (kismet_server.cc:2650); saved pc 0x4014b380
>  caller of frame at 0xbef09458
>  source language c++.
>  Arglist at 0xbef0faec, args: argc=-335704437, argv=0xcc814
>  Locals at 0xbef0faec, Previous frame's sp at 0xbef0fae4
>  Saved registers:
>   r4 at 0xbef0fac4, r5 at 0xbef0fac8, r6 at 0xbef0facc, r7 at 0xbef0fad0,
>   r8 at 0xbef0fad4, r9 at 0xbef0fad8, r10 at 0xbef0fadc, r11 at 0xbef0fae0,
>   lr at 0xbef0fae8, pc at 0xbef0fae8, f4 at 0xbef0fa94, f5 at 0xbef0faa0,
>   f6 at 0xbef0faac, f7 at 0xbef0fab8
>
>
> (gdb)
> (gdb) bt
> #0  0x00035be8 in Packetsourcetracker::SetTypeParms (this=0xeb07c,
>     in_types=@0xbef08dac, in_parm=<value optimized out>)
>     at packetsourcetracker.cc:759
> #1  0x0008b428 in ProcessBulkConf (conf=Cannot access memory at
> address 0xffffff38
> ) at kismet_server.cc:2098
> #2  0x000a76ac in main (argc=-335704437, argv=0xcc814) at
> kismet_server.cc:2650
> **************************************************************************
>