------- Comment #9 from lebedev at zhtw dot org dot ru 2006-11-04 10:40 ------- (In reply to comment #7) > Ok, thanks. Ideally, in case the problem unfortunately persists with current > GCC, it would be also useful if you could provide outputs from a debugging > session, because right now what happens after the output of the "forward" > string is a complete mystery... But this kind of "long distance" debugging is > hopeless, in general :( in case the problem persists we need someone able to > reproduce the problem on his machine and looking closely into it... >
I bootstrapped a fresh gcc-4.1.1. Bug has disapeared. So what do I do? Is this bug worth fixing in 3.6? I'm using netbsd's pkgsrc collection to build packages on Tru64. But the latest version of gcc in it is 3.6. I just don't like to install software outside the package system. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29696
