https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-01-14T00:51:54ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=2002006-01-14T00:51:54Zbuggs
<ul></ul><p>This is a known propolice bug for which we need to look upstream for a fix.</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=13652006-10-02T20:17:07Zcorecode
<ul></ul><p>does this still happen?</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=20582007-01-17T11:19:49Zcorecode
<ul></ul><p>closing:<br />no feedback from submitter + no new upstream patches for propolice</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=20932007-01-20T10:55:01Zelekktretterr
<ul></ul><p>Id like to open this bug again because I get the same thing but on <br />wip/powedns-recursor.</p>
<p>c++ -O -pipe -I/usr/pkg/include -I/usr/include -Wall -O3 <br />-I/usr/pkg/include -I/usr/include -c -o pdns_recursor.o pdns_recursor.cc<br />pdns_recursor.cc: In function `void <br />doResends(boost::multi_index::detail::index_iterator<boost::multi_index::detail::ordered_index_node<boost::multi_index::detail::ordered_index_node<boost::multi_index::detail::index_node_base<MTasker<PacketID, <br />std::string>::Waiter> > > >&, PacketID, const std::string&)':<br />pdns_recursor.cc:1139: internal compiler error: in <br />sweep_string_variable, at cc_prep/protector.c:1159<br />Please submit a full bug report,<br />with preprocessed source if appropriate.<br />See <URL:http://gcc.gnu.org/bugs.html> for instructions.</p>
[wrapper.sh] note: The real command line, after the pkgsrc wrapper, was:<br />/usr/obj/pkgsrc/wip/powerdns-recursor/work/.gcc/bin/g++ -O -pipe <br />-I/usr/obj/pkgsrc/wip/powerdns-recursor/work/.buildlink/include -Wall <br />-O3 -c -o pdns_recursor.o pdns_recursor.cc <br />-L/usr/obj/pkgsrc/wip/powerdns-recursor/work/.buildlink/lib<br />gmake: *** [pdns_recursor.o] Error 1
<ul>
<li>Error code 2</li>
</ul>
<p>Petr</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=20942007-01-20T11:22:01Zcorecode
<ul></ul><p>fixed</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=20952007-01-20T12:45:00Zmemmerto
<ul></ul><p>This is a problem with propolice, an add-on to gcc. Whatever this problem<br />is, it's not going to be fixed in the 3.4.x gcc stream. The patches I sent<br />you disable propolice while compiling powerdns-recursor.</p>
<p>I'm hoping that the propolice support in gcc-4.1 will not have this problem,<br />but more investigation is warranted.</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=20962007-01-20T12:50:01Zmemmerto
<ul></ul><p>sent</p>
<blockquote>
<p>you disable propolice while compiling powerdns-recursor.</p>
</blockquote>
<p>I spoke to soon. Thanks to corecode for tracking down a fix for this<br />problem.</p> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=21062007-01-21T02:45:00Zdillon
<ul></ul><p>:Simon 'corecode' Schubert <<a class="email" href="mailto:corecode@fs.ei.tum.de">corecode@fs.ei.tum.de</a>> added the comment:<br />:<br />:fixed<br />:<br />:----------<br />:status: chatting -> resolved</p>
<pre><code>Another propolice issue? I'm about ready to huck that thing out <br /> the window.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #53: gcc34 internal errorhttps://bugs.dragonflybsd.org/issues/53?journal_id=21092007-01-21T03:10:01Zcorecode
<ul></ul><p>As every new technology, it needs some time to evolve. Nevertheless, it is an important tool to mitigate the effects stack overflow attacks can produce. Besides, this was no code generation error, but a simple abort() in the compiler sources to handle unforseen circumstances. Gcc is full of those, as is our kernel. It is just not easy to make such a big project completely bug-free.</p>
<p>cheers<br /> simon</p>