Re: shared lib function call's parameters change by themselves??
From: Måns Rullgård (mru_at_kth.se)
Date: 10/24/03
- Next message: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Previous message: Dawid Oosthuizen: "Re: shared lib function call's parameters change by themselves??"
- In reply to: Dawid Oosthuizen: "Re: shared lib function call's parameters change by themselves??"
- Next in thread: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Reply: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 24 Oct 2003 13:20:28 +0200
Dawid Oosthuizen <4st.shadow@tuks.co.za> writes:
> FYI, the problem was a too small target buffer passed to the internal
> decoder, which then over-wrote some other memory... :(
The classical buffer overflow. Electric Fence is very helpful in
finding these errors. You'll find it somewhere on http://perens.com.
-- Måns Rullgård mru@kth.se
- Next message: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Previous message: Dawid Oosthuizen: "Re: shared lib function call's parameters change by themselves??"
- In reply to: Dawid Oosthuizen: "Re: shared lib function call's parameters change by themselves??"
- Next in thread: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Reply: Paul Pluzhnikov: "Re: shared lib function call's parameters change by themselves??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]