From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31438] New: gcc wiki crashes with Uhandled Exception
Date: Fri, 01 Mar 2024 17:31:45 +0000 [thread overview]
Message-ID: <bug-31438-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31438
Bug ID: 31438
Summary: gcc wiki crashes with Uhandled Exception
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: carlos at redhat dot com
Target Milestone: ---
During the Office Hours for the GNU Toolchain we were doing a live search for
cauldron notes on the wiki and it crashed.
The following URL crashes the wiki:
https://gcc.gnu.org/wiki/OfficeHours?action=fullsearch&context=180&value=cauldron&titlesearch=Titles
It is basically a title search for "cauldron", but it's odd that it crashes
with Uhandled Exception.
~~~
Unhandled Exception
An unhandled exception was thrown by the application.
~~~
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>Unhandled Exception</title>
</head><body>
<h1>Unhandled Exception</h1>
<p>An unhandled exception was thrown by the application.</p>
</body></html>
~~~
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-03-01 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 17:31 carlos at redhat dot com [this message]
2024-03-01 17:34 ` [Bug Infrastructure/31438] " pinskia at gcc dot gnu.org
2024-03-01 18:01 ` fche at redhat dot com
2024-03-01 22:21 ` mark at klomp dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31438-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).