Re: Re: SIGSEGV in 0.8.3

Helmut Wirth <[email protected]>
Newsgroups gmane.comp.kde.kwintv
Organization bison GmbH
Message-ID <[email protected]>
Hello Dirk,

the cl output from the cvs version doesn't look different to 0.8.3 either. I can't identify
a library related debug message or such (maybe its just me). I've doublechecked that i used the
binary from the cvs tree:

driver bttv, version 0x0000090f[wirth@pc001 wirth]$ kdetv -v
Qt: 3.1.2
KDE: 3.1.4-7 Red Hat
kdetv: post 0.8.3

And here is the output anyway:

[wirth@pc001 wirth]$ kdetv
Try to open v4l2 vbi device, libzvbi interface rev.
$Id: io-v4l2.c,v 1.12 2002/11/30 02:37:18 mschimek Exp $Opened /dev/vbi
Try to open v4l2 (2002-10) vbi device, libzvbi interface rev.
$Id: io-v4l2k.c,v 1.4 2003/02/16 18:58:07 mschimek Exp $Opened /dev/vbi
/dev/vbi (BT878 video (Leadtek WinFast 20PCI:01:09.0) is a v4l2 vbi device,
Current scanning system is 625
Querying current vbi parameters... success
VBI capture parameters granted: format 59455247, 35468950 Hz, 2048 bpl, offs 244, F1 7+16, F2 319+16, flags 00000000
Nyquist check passed
Request decoding of services 0x60000c7f
Will decode services 0x0000041f
Using streaming interface
Fifo initialized
Requesting streaming i/o buffers
Try to open v4l vbi device, libzvbi interface rev.
$Id: io-v4l.c,v 1.9 2002/11/30 02:37:18 mschimek Exp $Opened /dev/vbi
Driver name 'BT878 video (Leadtek WinFast 20'
Attempt to guess the videostandard
Driver supports VIDIOCGTUNER: 0
Videostandard is PAL/SECAM
/dev/vbi (BT878 video (Leadtek WinFast 20) is a v4l vbi device
Hinted video standard 0, guessed 625
Driver supports VIDIOCGVBIFMT, guessed videostandard 625
Accept current vbi parameters
Guessed videostandard 625
Nyquist check passed
Will decode services 0x0000041f
Warning: no read select, reading will block
Capture buffer allocated
Successful opened /dev/vbi (BT878 video (Leadtek WinFast 20)
kdetv: could not open config files /home/user/wirth/.lircrc and /etc/lircrc
kdetv: Datei oder Verzeichnis nicht gefunden
QDateTime::fromString: Parameter out of range.

Is there a special switch to enable further debugging? Btw., there is no difference
in behavior between compiling with / without lirc support, and the last output
"QDateTime::...." appears just after startup at a time at which the app runs smoothly.

Maybe we should keep further conversation private, i don't think that too much people
on the list are interested in my problem....

Ciao,
-- 
Helmut Wirth

[email protected]
-------------------------------------------------------------
bison GmbH                         phone +49 89 / 50 03 91-14
Planegger Str. 16                  fax   +49 89 / 50 03 91-17
D-82110 Germering                  http://www.bison-soft.de/
-------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.