IIRC you have to add "-ggdb" to make VDR & plugins with debugging symbols.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
I build from the hg source.
On 9/10/2012 9:20 AM, Dominic Evans wrote:
Hi Timothy,
On 29 August 2012 22:01, Timothy D. Lenz wrote:
Just did a crash to grab what is in the logs:
/var/log/
syslog:
Aug 29 13:57:01 x64VDR vdr: [9106] ATSC Scanner thread started (pid=20976,
tid=9106)
Aug 29 13:57
Hi Timothy,
On 29 August 2012 22:01, Timothy D. Lenz wrote:
> Just did a crash to grab what is in the logs:
>
> /var/log/
> syslog:
> Aug 29 13:57:01 x64VDR vdr: [9106] ATSC Scanner thread started (pid=20976,
> tid=9106)
> Aug 29 13:57:01 x64VDR kernel: ATSC Scanner[9106]: segfault at 7f9ca800010
Just did a crash to grab what is in the logs:
/var/log/
syslog:
Aug 29 13:57:01 x64VDR vdr: [9106] ATSC Scanner thread started
(pid=20976, tid=9106)
Aug 29 13:57:01 x64VDR kernel: ATSC Scanner[9106]: segfault at
7f9ca8000108 ip 7f9ca8000108 sp 7f9c9dc9cbc8 error 15
messages:
Aug 29 13
I don't mess with this enough to remember the steps for making the
dumps, but making it crash is as easy as telling it to scan for
channels. So if you want to put up the steps to get the data... :)
I'm using Debian x64 and I use putty/winscp to work with it.
On 8/28/2012 1:11 PM, Dominic Evans
On 28 Aug 2012, at 20:58, "Timothy D. Lenz" wrote:
> The crashing problem would be better address by making it part of VDR. I am
> trying to make scripts to use Schedules Direct because even if VDR was
> picking up what the broadcasters send, the broadcasters themselves are
> unreliable and ha
Yes, and there are programs that can capture part of a stream to a file
to examine. So you don't need access to the stream to see where the
broadcasters are failing to follow the FCC set standards. I think
Dvbsnoop is one and I have compiled, though I only used it once or twice
several years ag
http://www.fepg.org/
I suspect he ether got too busy to work on it anymore or just got tired
of of it. He put out several nice plugins in a short time back when the
US switched to ATSC.
On 8/28/2012 8:05 AM, Dominic Evans wrote:
On 25 August 2012 20:54, Timothy D. Lenz wrote:
The problem h
The crashing problem would be better address by making it part of VDR. I
am trying to make scripts to use Schedules Direct because even if VDR
was picking up what the broadcasters send, the broadcasters themselves
are unreliable and half assed at sending eit. But if the seg fault when
trying to
On Tue, Aug 28, 2012 at 8:05 AM, Dominic Evans wrote:
> On 25 August 2012 20:54, Timothy D. Lenz wrote:
>> The problem here in the US is, DVB is not a standard for anything.
>
> I'm guessing Klaus' problem here is that he doesn't live in the US so
> can't access ATSC broadcasts for testing, so it
On 25 August 2012 20:54, Timothy D. Lenz wrote:
> The problem here in the US is, DVB is not a standard for anything.
I'm guessing Klaus' problem here is that he doesn't live in the US so
can't access ATSC broadcasts for testing, so it doesn't really make
sense for him to attempt to maintain it in
The problem here in the US is, DVB is not a standard for anything.
On 8/25/2012 2:42 AM, Klaus Schmidinger wrote:
I don't think that problems would be fixed any better if this were
part of the official VDR code. If the original author no longer maintains
the code, somebody else should take over
On 25.08.2012 04:04, Timothy D. Lenz wrote:
ATSC is the standard for OTA broadcast in the US now. It would be nice if
support could be built into vdr now. The plugin for getting eit data and
scanning for channels hasn't been updated in 2 years. It still has problems. on
my x64 system, it seg f
ATSC is the standard for OTA broadcast in the US now. It would be nice
if support could be built into vdr now. The plugin for getting eit data
and scanning for channels hasn't been updated in 2 years. It still has
problems. on my x64 system, it seg faults most of the time when trying
to scan fo
14 matches
Mail list logo
