From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Olcay Korkmaz <olcay.krkmz@gmail.com>
Cc: linux-media@vger.kernel.org, Gregor Jasny <gjasny@googlemail.com>
Subject: Re: bug: dvbv5-scan segfaults
Date: Tue, 27 Aug 2019 14:19:52 -0300 [thread overview]
Message-ID: <20190827141952.19d5e3d4@coco.lan> (raw)
In-Reply-To: <CADBDwkcPtEWA6nBFGwdQQn5USzxHNvvoczSY8sRBP1hnB6Y7hw@mail.gmail.com>
Em Tue, 27 Aug 2019 19:49:41 +0300
Olcay Korkmaz <olcay.krkmz@gmail.com> escreveu:
> > Ok, the problem is happening here:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > dvb_store_channel (dvb_file=0x7fffffffe460, __p=0x5555555605d0, dvb_scan_handler=0x555555565060, get_detected=0,
> > get_nit=0) at dvb-file.c:1345
> > 1345 if (dvb_scan_handler->nit->transport) {
> > (gdb) bt
> > #0 dvb_store_channel (dvb_file=0x7fffffffe460, __p=0x5555555605d0, dvb_scan_handler=0x555555565060, get_detected=0,
> > get_nit=0) at dvb-file.c:1345
> > #1 0x0000555555556847 in run_scan (dvb=0x5555555604f0, args=0x7fffffffe4b0) at dvbv5-scan.c:313
> > #2 main (argc=<optimized out>, argv=<optimized out>) at dvbv5-scan.c:562
> >
> > The enclosed patch should fix the issue. Could you please check?
>
> Thanks, patch fixed the problem.
Great!
Patch applied to master and to stable-1.16 and stable-1.14 branches:
https://git.linuxtv.org/v4l-utils.git/commit/?h=stable-1.14&id=0622c6d3592efa4817cfba148c64bd034baa2420
https://git.linuxtv.org/v4l-utils.git/commit/?h=stable-1.16&id=7c0eda007e698c5d2cbfb9fb33bb2472551ec46d
https://git.linuxtv.org/v4l-utils.git/commit/?id=58edfe080b1442c274c85b98cb6e7374c28695cf
Gregor,
Could you please place them on a next stable release for 1.14 and 1.16?
Thanks,
Mauro
prev parent reply other threads:[~2019-08-27 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 16:59 bug: dvbv5-scan segfaults Olcay Korkmaz
2019-08-26 17:40 ` Mauro Carvalho Chehab
2019-08-26 19:25 ` Olcay Korkmaz
2019-08-27 13:09 ` Mauro Carvalho Chehab
2019-08-27 16:49 ` Olcay Korkmaz
2019-08-27 17:19 ` Mauro Carvalho Chehab [this message]
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=20190827141952.19d5e3d4@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=olcay.krkmz@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.