Re: [superh-gnu-discuss] mplayer argument parsing segfault with 4.4-45
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [superh-gnu-discuss] mplayer argument parsing segfault with 4.4-45
- To: Bill Traynor <wmat@xxxxxxx>
- Subject: Re: [superh-gnu-discuss] mplayer argument parsing segfault with 4.4-45
- From: Magnus Damm <magnus.damm@xxxxxxxxx>
- Date: Tue, 5 Jan 2010 12:58:02 +0900
Hi everyone,
[CC Matt]
On Tue, Jan 5, 2010 at 5:56 AM, Bill Traynor <wmat@xxxxxxx> wrote:
> On Tue, Dec 29, 2009 at 11:21, Mark Mitchell <mark@xxxxxxxxxxxxxxxx> wrote:
>>
>> Magnus Damm wrote:
>>
>> > The mplayer source is fairly large so I suspect that the issue needs
>> > to be tracked down further. Do you have any pointer to a more fine
>> > grained step by step document that can be followed to produce these
>> > things for you? I'm quite busy though so I'm afraid I'll just add this
>> > to my TODO list for now.
>>
>> The first technique is to mix object files between the good and bad
>> builds. Build the whole thing with both compilers, but then link half
>> of the object files from the good build with the other half from the bad
>> build. Continue to bisect things until you have a bad object file. If
>> you're lucky, that's a small object file with just one or two functions
>> in it, and it will be obvious what's been miscompiled -- or what's buggy
>> in the source code.
>
> This was posted to mplayer-dev-eng. I'm posting here to complete the
> thread. This is not a compiler bug, but a mplayer bug. Matt Fleming and I
> figured this out, here's the explanation and patch authored by Matt:
> Attached is a patch that changes the snippet of code that tests for the
> presence of vsscanf() during configure.
I just tested mplayer svn r30223 and it compiles and runs as expected
with 4.4-45. Many thanks to you all for tracking down and fixing this
issue!
Cheers,
/ magnus