qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Capture network traffic
Date: Sun, 20 Jan 2008 02:30:29 +0100	[thread overview]
Message-ID: <fb249edb0801191730q49ee0336ka5f65fe7976de34d@mail.gmail.com> (raw)
In-Reply-To: <803877.27585.qm@web57007.mail.re3.yahoo.com>

Hi,

On 18/12/2007, Balazs Attila-Mihaly (Cd-MaN) <x_at_y_or_z@yahoo.com> wrote:
> Here goes version 0.3 of my packet capture patch. I rewritten it to be a custom VLANClient which implements the capturing part in its fd_read proceudre, rather than adding additional properties to the VLAN structure. Monitor support is also present.

You can't cast the result of get_param_value() to char * because (as
expected) you get this:

[balrog@borg qemu-cvs]$ x86_64-softmmu/qemu-system-x86_64 -net
capture,file=out a
Segmentation fault

Also I'm sure the use of asprintf() will upset the non-Linux-or-BSD
users. I don't think you need to check for memory allocation failures
(the message will not display anyway in such case, because monitor
allocates memory for that). It will be nice if you can remove stray
spaces on end of lines/empty lines. The PCAPHeader struct probably
should have a __packed__ attribute.

Thanks,
Andrew

  reply	other threads:[~2008-01-20  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  7:36 [Qemu-devel] [PATCH] Capture network traffic Balazs Attila-Mihaly (Cd-MaN)
2008-01-20  1:30 ` andrzej zaborowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-18 15:51 Balazs Attila-Mihaly (Cd-MaN)

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=fb249edb0801191730q49ee0336ka5f65fe7976de34d@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).