On Tue, Oct 11, 2005 at 10:17:55AM +0530, R.Ramkumar wrote:
> > Why are you not using gcc-4.0 4.0.2-2, the current version of gcc-4.0 in
> > unstable?
> I generally go with the testing packages.. should I be reporting the
> bugs only with the unstable version?
When you are going to claim that a core package is broken to the point of
being unreleasable, it is very important to know what version of the package
is actually affected. It's also pretty bold to claim that gcc is completely
unreleasable when most of the base system in unstable has been rebuilt with
gcc-4.0 and works fine; it seems equally as likely that gcc-4.0 is exposing
a bug in the gtkboard source.
Anyway, your bug is a gtkboard bug, in menu_start_game():
Yeah, this smashes the stack. Just because it worked with gcc-3.3 doesn't
mean this is a gcc-4.0 bug.
--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/
--vkogqOf2sHV7VnPd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Tue, 11 Oct 2005 00:14:32 -0700
From: Steve Langasek <email address hidden>
To: "R.Ramkumar" <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#333119: gcc-4.0: Segfaulting code generated for gtkboard-0.11pre0
--vkogqOf2sHV7VnPd Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
reassign 333118 gtkboard
severity 333118 grave
thanks
On Tue, Oct 11, 2005 at 10:17:55AM +0530, R.Ramkumar wrote:
> > Why are you not using gcc-4.0 4.0.2-2, the current version of gcc-4.0 in
> > unstable?
> I generally go with the testing packages.. should I be reporting the
> bugs only with the unstable version?
When you are going to claim that a core package is broken to the point of
being unreleasable, it is very important to know what version of the package
is actually affected. It's also pretty bold to claim that gcc is completely
unreleasable when most of the base system in unstable has been rebuilt with
gcc-4.0 and works fine; it seems equally as likely that gcc-4.0 is exposing
a bug in the gtkboard source.
Anyway, your bug is a gtkboard bug, in menu_start_game():
[...]
for (i=3D0; i<4; i++)
help_ items[i] .accelerator =3D NULL;
help_ items[i] .callback =3D menu_show_game_doc;
help_ items[i] .item_type =3D "";
{
}
Yeah, this smashes the stack. Just because it worked with gcc-3.3 doesn't
mean this is a gcc-4.0 bug.
--=20 www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://
--vkogqOf2sHV7VnPd pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
ufymYLloRAsLwAJ 0a51ioCeCWzpB2L UYWKwVUzIa8tgCg vQpO vb+nF5FkCePCw=
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDS2ZYKN6
krwKZjKjg+
=JVsO
-----END PGP SIGNATURE-----
--vkogqOf2sHV7V nPd--