From: Mark Purcell <mark@purcell.id.au>
To: linux-media@vger.kernel.org
Cc: Vincent Pelletier <plr.vincent@gmail.com>,
606728-forwarded@bugs.debian.org
Subject: Fwd: Bug#606728: dvbscan: Infinite loop parsing arguments
Date: Sun, 13 May 2012 20:11:43 +1000 [thread overview]
Message-ID: <201205132011.44898.mark@purcell.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
---------- Forwarded Message ----------
Subject: Bug#606728: dvbscan: Infinite loop parsing arguments
Date: Sat, 11 Dec 2010, 21:13:08
From: Vincent Pelletier <plr.vincent@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Package: dvb-apps
Version: 1.1.1+rev1355-1
Severity: normal
Tags: patch
How to reproduce:
dvbscan -out raw - some_file
Result:
dvbscan process taking 100% of cpu.
Cause:
Argument parser doesn't increment argument position when
encountering -out parameter, so it loops forever on parsing -out.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.36vin0 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages dvb-apps depends on:
ii libc6 2.11.2-7 Embedded GNU C Library: Shared
lib
ii udev 164-2 /dev/ and hotplug management
daemo
dvb-apps recommends no packages.
dvb-apps suggests no packages.
-- no debconf information
-----------------------------------------
[-- Attachment #2: dvbscan.c.diff --]
[-- Type: text/x-diff, Size: 301 bytes --]
--- dvbscan.c.org 2010-12-11 11:00:22.000000000 +0100
+++ dvbscan.c 2010-12-11 11:00:05.000000000 +0100
@@ -225,6 +225,7 @@
output_filename = argv[argpos+2];
if (!strcmp(output_filename, "-"))
output_filename = NULL;
+ argpos+=3;
} else {
if ((argc - argpos) != 1)
usage();
reply other threads:[~2012-05-13 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201205132011.44898.mark@purcell.id.au \
--to=mark@purcell.id.au \
--cc=606728-forwarded@bugs.debian.org \
--cc=linux-media@vger.kernel.org \
--cc=plr.vincent@gmail.com \
/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.