[vdr] Segfault with xine-0.7.9

[Gregoire Favre]

On Sun, Nov 12, 2006 at 01:50:51PM +0100, Reinhard Nissl wrote:
> Hi,
> 
> Gregoire Favre wrote:
> 
> >Any idea what I shall change ?
> 
> Find the following two lines in xineLib.c
> 
> 	#define ASSERT_PALETTE(x)
> 	//#define ASSERT_PALETTE(x) x
> 
> and change them to
> 
> 	//#define ASSERT_PALETTE(x)
> 	#define ASSERT_PALETTE(x) x
> 
> Maybe a debug message appears before the segfault.

No, it's directly the 
"Segmentation fault (core dumped)" with your change it comes later on.
And I think it's the same with your modification :

Program terminated with signal 11, Segmentation fault.
#0  0x00002b9b73805a8a in PluginXine::cXinePalette::cEntry::getIndex (this=0x300f30)
    at xineLib.c:331
331             return m_index;
(gdb) bt
#0  0x00002b9b73805a8a in PluginXine::cXinePalette::cEntry::getIndex (this=0x300f30)
    at xineLib.c:331
#1  0x00002b9b7380427b in ScaleBitmapHQ (src=0x2bb3900 "°Ä\004", x0=25, y0=50, w=672, 
    h=465, stride=672, ws=503, hs=426, x1=26, y1=40, w1=439, h1=341, transparentIndex=1, 
    colors=0x24009b8, numColors=8, palette2=@0x7fff392dfc60, paletteSize=@0x7fff392dfc5c, 
    currentPaletteSize=16, currentPalette=0x23c35b0, xineLib=0x23bed78) at xineLib.c:1245
#2  0x00002b9b73804aa8 in PluginXine::cXineLib::execFuncOsdDrawBitmap (this=0x23bed78, 
    needsScaling=PluginXine::cXineLib::yes, videoWidth=503, videoHeight=426, 
    xineOsd=0x24011d0, window=0, bitmap=0x24009b0, x=13, y=5, width=627, height=460, 
    stride=672) at xineLib.c:1570
#3  0x00002b9b73805666 in PluginXine::cXineLib::sendWindow (this=0x23bed78, 
    xineOsd=0x24011d0, windowNum=0, bitmap=0x24009b0, videoLeft=20, videoTop=75, 
    videoWidth=503, videoHeight=426, videoZoomX=108, videoZoomY=135, dontOptimize=false)
    at xineLib.c:1849
#4  0x00002b9b73805818 in PluginXine::cXineLib::SendWindow (this=0x23bed78, 
    xineOsd=0x24011d0, windowNum=0, bitmap=0x24009b0, videoLeft=0, videoTop=0, 
    videoWidth=544, videoHeight=576, videoZoomX=108, videoZoomY=135, dontOptimize=false)
    at xineLib.c:1690
#5  0x00002b9b73807191 in PluginXine::cXineOsd::Flush (this=0x24011d0) at xineOsd.c:356
#6  0x00000000004da3ea in cSkinSTTNGDisplayMenu::Flush (this=0x2401100) at skinsttng.c:646
#7  0x00000000004d130f in cSkins::Flush (this=0x74e580) at skins.c:356
#8  0x00000000004837c6 in cInterface::GetKey (this=0x19c88d0, Wait=true) at interface.c:35
#9  0x00000000004f747a in main (argc=17, argv=0x7fff392e0788) at vdr.c:866
Current language:  auto; currently c++

> Another idea is to use valgrind on vdr to see whether there are any 
> memory corruptions in vdr-xine.

I'll try to undestand how then...

Thank,
-- 
Grégoire FAVRE  http://gregoire.favre.googlepages.com  http://www.gnupg.org