This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [wwwdocs] segfault.html (was Synthetic register related: Seg fault) - segfault.html [1/1]
On Thu, Jan 16, 2003 at 11:46:30AM -0500, Kelley Cook wrote:
> [This followup was posted to gmane.comp.gcc.devel and a copy
> was sent to the cited author.]
>
> In article <20030115194943.A16830@hg.cs.mu.OZ.AU>,
> fjh@cs.mu.OZ.AU says...
> > On 15-Jan-2003, Andy Walker <ja_walker@earthlink.net> wrote:
> > > What would be the best approach to hunting down flaws that cause things like
> > > this Segmentation fault?
>
> I'm pretty sure this would make a good web page addition.
> Likely should be linked onto the bugs.html page.
>
> So here it is.
Cool! I was thinking of turning that into a web page but you beat me
to it.
Lots of suggestions:
o The DOCTYPE stuff isn't included in the files that are in
wwwdocs/htdocs, but is added by a tool before they are copied to
the web pages.
o The web pages themselves don't specify styles; Gerald can provide
more information about that.
o Web pages don't generally say who wrote them, although that info
can be in the CVS log.
o The title is rather long; how about "How to Debug a GCC Seg Fault."
o Our other howto documents are called *-howto.html.
Gerald suggested that I create a new directory called bugs and move the
current bugs.html to bugs/index.html, updating all of the places that
reference the current file. Then reghunt-howto can be moved there, plus
the document Wolfgang is writing about minimizing test cases, and now
this new one. Another thing I'd like to see there is how to identify
code (from a large app) that fails for particular optimizations.
Janis