How do I submit a gcc bug?

[Lindley]

So, I managed to make gcc 4.5.0 choke, probably on my use of decltype. I got this nice message:

g++: Internal error: Segmentation fault (program cc1plus)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

I checked out that page, and generated the preprocessed files and dumped the build output to a file, all as they asked.

But now I'm trying to figure out how to actually submit the thing.....and I have no idea.

They mention two options: Submit it directly to bugzilla, or use the gccbug script.

Well, Bugzilla's submission form does not seem to contain a method to attach a file, so that's pretty useless. And if there's any documentation at all for gccbug, I haven't been able to find it.

Anyone here know the process?

[treuss]

In Bugzilla you certainly can attach files. It might be that you first need to submit the report though.

Check some of the existing bugs: There's a "Create a new attachment" link.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323

[monarch_dodra]

So, did you submit it?

Can you provide a bug number or link, for those most curious.

[Lindley]

In Bugzilla you certainly can attach files. It might be that you first need to submit the report though.

Check some of the existing bugs: There's a "Create a new attachment" link.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323

Thanks, I'll try that. However, I'm not sure what they want in the "Host triplet", "Target triplet", and "Build triplet" fields of the creation form. Any insight?

Can you provide a bug number or link, for those most curious.

I will when it's in. It appears to be a problem using a typedefed decltype in a lambda expression, judging by my stripped-down test case.

[Lindley]

Hmm, I suspect it wants x86_64-linux-unknown-gnu for all three.

Bug #44366.