From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] segmentation fault running kismet
Date: Fri, 08 Feb 2008 09:08:41 +0100 [thread overview]
Message-ID: <47AC0E09.7030800@gmail.com> (raw)
In-Reply-To: <26b26d180802072251w7c06a39es337ee76936182b96@mail.gmail.com>
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."
next prev parent reply other threads:[~2008-02-08 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 6:51 [Buildroot] segmentation fault running kismet saurav barik
2008-02-08 8:08 ` Joe [this message]
2008-02-08 8:51 ` saurav barik
2008-02-12 7:04 ` saurav barik
-- strict thread matches above, loose matches on Subject: below --
2008-02-07 16:31 Saurav Kumar Barik
2008-02-07 17:16 ` Joe
2008-02-08 5:05 ` Yogesh Kumar Sharma
2008-02-08 7:08 ` Ulf Samuelsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47AC0E09.7030800@gmail.com \
--to=zentrale.at.work@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox