New submission from Ronald S. Bultje <[email protected]>:

$ gdb ./ffplay_g
(gdb) r rtsp://stream.zune.net:554/a4241/e3/033/984/819/at/audio.wma
Starting program: /Users/ronaldbultje/Projects/ffmpeg-svn/x86-
64/ffplay_g rtsp://stream.zune.net:554/a4241/e3/033/984/819/at/audio.wma
[..]
FFplay version SVN-r26050, Copyright (c) 2003-2010 the FFmpeg developers
  built on Dec 17 2010 21:53:08 with gcc 4.2.1 (Apple Inc. build 5664)
  configuration: --samples=/Users/ronaldbultje/Movies/fate-suite --
enable-gpl
  libavutil     50.34. 0 / 50.34. 0
  libavcore      0.16. 0 /  0.16. 0
  libavcodec    52.99. 1 / 52.99. 1
  libavformat   52.88. 0 / 52.88. 0
  libavdevice   52. 2. 2 / 52. 2. 2
  libavfilter    1.69. 0 /  1.69. 0
  libswscale     0.12. 0 /  0.12. 0
[asf @ 0x10105e000] Ext DRM protected stream detected, decoding will 
likely fail!
[asf @ 0x10105e000] DRM protected stream detected, decoding will likely 
fail!
[asf @ 0x10105e000] Digital signature detected, decoding will likely 
fail!
[rtsp @ 0x10104b200] method SETUP failed: 461 Unsupported Transport

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000180
[Switching to process 72662]
ff_rtp_queued_packet_time (s=0x0) at 
/Users/ronaldbultje/Projects/ffmpeg-svn/libavformat/rtpdec.c:619
619         return s->queue ? s->queue->recvtime : 0;

gdb) bt
#0  ff_rtp_queued_packet_time (s=0x0) at 
/Users/ronaldbultje/Projects/ffmpeg-svn/libavformat/rtpdec.c:619
#1  0x000000010008d461 in ff_rtsp_fetch_packet (s=0x10104b200, 
pkt=0x116772930) at /Users/ronaldbultje/Projects/ffmpeg-
svn/libavformat/rtsp.c:1559
(gdb) print s
$1 = (RTPDemuxContext *) 0x0
(gdb) 

Not sure where the NULL check should be, but a crash is always 
unacceptable.

----------
messages: 13045
priority: normal
status: new
substatus: new
title: Crash in RTP packet reordering code
type: bug

________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/issue2448>
________________________________________________

Reply via email to