[MPlayer-users] Annoying new message from CVS mplayer

The Wanderer inverseparadox at comcast.net
Tue Jul 1 02:54:30 CEST 2003


Sascha Sommer wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]

<snip>

>>L3: BigValues too large, doesn't make sense 416 384
>>
>>The numbers given are the most common, but do vary.

<snip>

>>I've tracked this down to mp3lib/layer3.c, where the message is printed 
>>in two different locations, both delimited by #ifdef L3_DEBUG #endif. 
>>Commenting out both of those blocks removes the message, without 
>>breaking the compile or appearing to affect functionality.
>>
>>Near the beginning of the file, there are these three lines:
>>
>>#if 0
>>#define L3_DEBUG 1
>>#endif
>>
>>Commenting out this block breaks the compile.
>>
>>I have been assured that, as seems intuitive, #if 0 will always be 
>>false; however, this does not seem consistent with this case, as if it 
>>were false then removing the block by commenting it out should not 
>>change anything.
> 
> The same message appears again a few lines later. The #ifdefs were
> commented out there. I reenabled them now.

Yes, I noticed - as I said, the message is printed in two different 
locations.

For some stupid reason, it hadn't occurred to me that only one of them - 
the non-#ifdef'ed one - might be responsible for this... so much for my 
vaunted intellect. Thanks.

(This still doesn't explain why commenting out something which would 
never be included anyway broke the compile, but that's another issue...)

-- 
       The Wanderer

A government exists to serve its citizens, not to control them.



More information about the MPlayer-users mailing list