public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13218] GDB always segfaults on Linux 3.0 and ARM
Date: Mon, 10 Oct 2011 17:22:00 -0000 [thread overview]
Message-ID: <bug-13218-4717-iBnjDVFTqz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13218-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13218
Ulrich Weigand <uweigand at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |uweigand at gcc dot gnu.org
--- Comment #2 from Ulrich Weigand <uweigand at gcc dot gnu.org> 2011-10-10 17:22:02 UTC ---
(In reply to comment #1)
> I'm not seeing where any of those os_FOO values are used. Can we just garbage
> collect all of that?
Agreed. This has been in since the beginning of CVS history, and was
apparently never used even then.
I'll prepare a patch to remove this routine.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-10-10 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 20:53 [Bug gdb/13218] New: " johannespfau at gmx dot de
2011-09-23 13:46 ` [Bug gdb/13218] " pedro at codesourcery dot com
2011-10-10 17:22 ` uweigand at gcc dot gnu.org [this message]
2011-10-10 17:23 ` uweigand at gcc dot gnu.org
2011-10-10 18:49 ` cvs-commit at gcc dot gnu.org
2011-10-10 18:53 ` uweigand at gcc dot gnu.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-13218-4717-iBnjDVFTqz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).