From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iw packaging
Date: Tue, 16 Sep 2008 16:50:08 -0400 [thread overview]
Message-ID: <1221598208.17084.11.camel@dv> (raw)
In-Reply-To: <1221596962.9262.12.camel@johannes.berg>
On Tue, 2008-09-16 at 22:29 +0200, Johannes Berg wrote:
> Hi,
>
> I've just tagged iw version 0.9 (and 0.9.1 after a small build fix)
> because I think the tool is now actually usable in a limited way, unlike
> before where it would never properly report errors etc.
>
> Anyone want to pick it up for the various distros?
Sorry for diverting the thread, but the current git head (which is
tagged as 0.9.1) is broken.
$ ./iw
Usage: ./iw [options] command
Options:
--debug enable netlink debugging
--version show version
Commands:
list
Segmentation fault (core dumped)
Debugging shows:
82 fprintf(stderr, "Commands:\n");
(gdb)
Commands:
83 for (cmd = &__start___cmd; cmd < &__stop___cmd; cmd++) {
(gdb) p __start___cmd
$1 = {section = 0x0, name = 0x403d02 "info", args = 0x0, cmd = NL80211_CMD_GET_WIPHY,
nl_msg_flags = 0, idby = CIB_PHY, handler = 0x402403 <handle_info>}
(gdb) p *(&__start___cmd + 1)
$2 = {section = 0x0, name = 0x0, args = 0x0, cmd = 4209927, nl_msg_flags = 0, idby = CIB_NONE,
handler = 0x30000000001}
(gdb)
That means, __start___cmd points to "info". The next command has no
name (and appears to be a complete mess). The clever section trick
doesn't seem to work properly.
I'm using Fedora 9 x86_64 with all updates.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-09-16 20:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 20:29 iw packaging Johannes Berg
2008-09-16 20:46 ` Stefanik Gábor
2008-09-16 20:50 ` Pavel Roskin [this message]
2008-09-16 21:11 ` Johannes Berg
2008-09-16 21:15 ` Johannes Berg
2008-09-16 21:23 ` Pavel Roskin
2008-09-16 21:38 ` Johannes Berg
2008-09-16 21:48 ` Pavel Roskin
2008-09-16 21:56 ` Johannes Berg
2008-09-16 22:14 ` Johannes Berg
2008-09-16 23:20 ` Pavel Roskin
2008-09-17 7:30 ` Johannes Berg
2008-09-17 10:41 ` Jochen Friedrich
2008-09-17 10:43 ` Johannes Berg
2008-09-17 11:05 ` "Adam Cécile (Le_Vert)"
2008-09-17 11:07 ` Johannes Berg
2008-09-17 11:11 ` "Adam Cécile (Le_Vert)"
2008-09-17 11:18 ` Johannes Berg
2008-09-17 11:25 ` Johannes Berg
2008-09-17 20:19 ` Stefanik Gábor
2008-09-17 20:31 ` Johannes Berg
2008-09-17 21:46 ` Davide Pesavento
2008-09-17 21:51 ` Stefanik Gábor
2008-09-17 21:52 ` Johannes Berg
2008-09-17 21:58 ` Stefanik Gábor
2008-09-17 22:03 ` Luis R. Rodriguez
2008-09-17 22:06 ` Stefanik Gábor
2008-09-17 22:07 ` Johannes Berg
2008-09-17 22:04 ` Johannes Berg
2008-09-17 16:23 ` Marcel Holtmann
2008-09-17 16:43 ` Johannes Berg
2008-09-17 18:06 ` Johannes Berg
2008-09-17 19:23 ` Luis R. Rodriguez
2008-09-17 23:36 ` Marcel Holtmann
2008-09-17 23:42 ` Johannes Berg
2008-10-10 21:25 ` Thomas d'Otreppe
2008-09-18 8:09 ` Helmut Schaa
2008-09-27 16:59 ` Davide Pesavento
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=1221598208.17084.11.camel@dv \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.