On Sun, 23 May 2010 05:26:47 +0200, Thomas Orgis wrote:
> I fixed the pointer alignment code now to operate on the pointer value
> via uintptr_t, which should be "proper" enough. It fixes the crash in
> my virtual machine.
Cool!
> Please have a go with
> http://mpg123.org/download/mpg123-1.12.2
Am Sun, 23 May 2010 02:41:04 +0400 (MSD)
schrieb William Pitcock :
> Both. I believe this is caused by a bug where the pointers appear to
> become realigned twice (e.g. to the next 16 bytes.) So I believe the
> second realignment is a bug that has always been there.
Though that assumption prove
Hi,
- "Thomas Orgis" wrote:
> Am Sat, 22 May 2010 03:43:28 +0400 (MSD)
> schrieb William Pitcock :
>
> > This is due to a memory alignment issue in the way that the struct
> is packed.
> > With some help from an affected user, we bisected it to mpg123 SVN
> r2491.
>
> OK, that revision re
Am Sat, 22 May 2010 03:43:28 +0400 (MSD)
schrieb William Pitcock :
> This is due to a memory alignment issue in the way that the struct is packed.
> With some help from an affected user, we bisected it to mpg123 SVN r2491.
OK, that revision replaced aligned memory blocks that relied on special
c
On Sat, 22 May 2010 03:43:28 +0400, William Pitcock wrote:
> This is due to a memory alignment issue in the way that the struct is packed.
> With some help from an affected user, we bisected it to mpg123 SVN r2491.
>
> When r2491 is backed out (using the attached patch), this bug does not show
>
tags 580095 + patch
thanks
Hi,
This is due to a memory alignment issue in the way that the struct is packed.
With some help from an affected user, we bisected it to mpg123 SVN r2491.
When r2491 is backed out (using the attached patch), this bug does not show up.
The reason why is because some o
6 matches
Mail list logo
