crash when streaming: what data needed for bug report?

[MikeInMass]

I am trying to stream video over the network from a Hauppauge PVR-350 TV card using vlc.
The release build of vlc 0.8.6h works fine for anywhere from a minute to an hour or so with this command line:

Code: Select all

C:\VideoLAN>\videolan\vlc\vlc --extraintf=logger -vvv dshow:// :dshow-vdev="Hauppauge WinTV PVR PCI II Capture" :dshow-adev="none" :sout="#transcode{vcodec=DIV3,vb=354,ab=32,scale=1,acodec=mp3,channels=1,deinterlace}:standard{access=mmsh,m ux=asf,dst=:8080}"

Then it crashes. The "--extraintf=logger" output shows no particularly interested error messages at the end, but the log file itself is partially corrupted! An extract from the corrupted log file is below. Mind you, this occurs after over 700k of benign error messages with no obvious corruption in the text.

Code: Select all

0000000 6765706d 6475615f 64206f69 67756265 m p e g _ a u d i o d e b u g 0000020 6d65203a 74616c75 73206465 74726174 : e m u l a t e d s t a r t 0000040 65646f63 706d0a0d 615f6765 6f696475 c o d e \r \n m p e g _ a u d i o 0000060 62656420 203a6775 6c756d65 64657461 d e b u g : e m u l a t e d 0000100 61747320 6f637472 0a0d6564 6e69616d s t a r t c o d e \r \n m a i n 0000120 72617720 676e696e 616c203a 62206574 w a r n i n g : l a t e b 0000140 65666675 6f662072 756d2072 6e692078 u f f e r f o r m u x i n 0000160 20747570 33393428 0d293337 3e01b00a p u t ( 4 9 3 7 3 ) \r \n ° 001 > 0000200 62656420 203a6775 6574616c 63697020 d e b u g : l a t e p i c 0000220 65727574 696b7320 64657070 39332820 t u r e s k i p p e d ( 3 9 0000240 38373633 b00a0d29 2004fd99 75626564 3 6 7 8 ) \r \n ° 231 ý 004 d e b u 0000260 c0203a67 0a0d3e03 203e0188 6e726177 g : À 003 > \r \n 210 001 > w a r n 0000300 3a676e69 0c4ad020 25b23005 74705f05 i n g : Ð J \f 005 0 ² % 005 _ p t 0000320 3d212073 73746420 36312820 29383732 s ! = d t s ( 1 6 2 7 8 ) 0000340 03180a0d 6564203e 3a677562 74616c20 \r \n 030 003 > d e b u g : l a t 0000360 69702065 72757463 6b732065 65707069 e p i c t u r e s k i p p e 0000400 33282064 32333533 0a0d2933 6e69616d d ( 3 3 5 3 2 3 ) \r \n m a i n 0000420 72617720 676e696e 4ad8203a 73200590 w a r n i n g : Ø J 220 005 s 0000440 68636e79 77206f72 696e7261 203a676e y n c h r o w a r n i n g : 0000460 20737470 63203d21 65727275 645f746e p t s ! = c u r r e n t _ d 0000500 20657461 36312d28 29393732 9fb00a0d a t e ( - 1 6 2 7 9 ) \r \n ° Ÿ 0000520 2c1004a1 747504e5 6172745f 6f63736e ¡ 004 020 , å 004 u t _ t r a n s c o 0000540 64206564 67756265 03a0203a 980a0d3e d e d e b u g : 003 > \r \n 230 0000560 64203e01 67756265 0000203a 001 > d e b u g : \0 \0

I tried again with the trunk-20080821-0004 nightly. It failed completely-- vlc running on the same machine as the server is unable to open the stream, saying that the server is not running.

What do I need to include to file a bug report for this that someone will actually look at? Does someone need to send me a debug build?

[Rémi Denis-Courmont]

A good bug report is easy to reproduce, and include a full detailled backtrace of the crash. And it is filed against the development version.

[MikeInMass]

A good bug report is easy to reproduce, and include a full detailled backtrace of the crash.

How do I get a backtrace under Windows?

And it is filed against the development version.

Sadly, with the development version my clients can't even connect. Am I doing something wrong?

[Rémi Denis-Courmont]

How do I get a backtrace under Windows?

Don't ask me.