Hello, 17 липня 2006 о 17:26 -0300 Tiago Macambira написав(-ла): > This is not a bug in systemtap, per see, but rather a bug in gcc 4.0.x. > But since this is the default compiler in sid now systemtap should try > to aliviate this issue depending on gcc (version >=4.1) or conflict with > known buggy gcc versions.
Thanks for report, but as you wrote it is bug in gcc-4.0 and it should
be fixed there. I do not think that depending on or conflicting with gcc
version is good idea. Depending on particular gcc versions does not
garanty that this version will be used for building the running kernel
and so systemtap probes (it can be changed in kernel's Makefile).
Conflicting with gcc versions makes those versions uninstalable for no
good reason - gcc used for building the kernel can be changed even
without that, and if kernel was built with buggy gcc - it cannot be
debugged anyway.
> Perhaps systemtap should be removed from sid
> untill gcc 4.1 is available for it.
packages.debian.org shows:
Package gcc-4.1
* testing (devel): The GNU C compiler
4.1.1-5: alpha amd64 arm hppa i386 ia64 m68k mips mipsel
powerpc s390 sparc
So I see no reason to remove systemtap from testing due to this (and
remember that kernel can be build with non-default compiler too).
So I see several possible solutions now:
1. leave this bug as remainder, and wait until gcc-4.0 fixed
2. add notes to README.Debian
3. both 1 and 2
Regards,
--
Eugeniy Meshcheryakov
signature.asc
Description: Digital signature
