public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libobjc/11433] Crash due to dereferencing null pointer when querying protocol
Date: Tue, 02 Dec 2003 00:45:00 -0000 [thread overview]
Message-ID: <20031202004529.5700.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030704113807.11433.richard@brainstorm.co.uk>
------- Additional Comments From gdr at integrable-solutions dot net 2003-12-02 00:45 -------
Subject: Re: Crash due to dereferencing null pointer when querying protocol
"zack at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| Patch applied to mainline.
|
| This is not a regression - the bug has been around since 2.95 - but
| the fix is very low risk so it might be a 3.3 candidate anyway.
| But that's not my decision. Closing bug.
I'm accpeting non-regression fixes too, til December 31.
If you have any chance to apply it to 3_3-branc, that would be
appreciated.
Thanks,
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11433
next prev parent reply other threads:[~2003-12-02 0:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 11:38 [Bug libobjc/11433] New: " richard at brainstorm dot co dot uk
2003-07-04 17:15 ` [Bug libobjc/11433] " pinskia at physics dot uc dot edu
2003-07-04 20:01 ` richard at brainstorm dot co dot uk
2003-08-23 0:43 ` dhazeghi at yahoo dot com
2003-10-30 7:08 ` pinskia at gcc dot gnu dot org
2003-12-01 23:06 ` zack at gcc dot gnu dot org
2003-12-01 23:30 ` cvs-commit at gcc dot gnu dot org
2003-12-01 23:31 ` zack at gcc dot gnu dot org
2003-12-02 0:45 ` gdr at integrable-solutions dot net [this message]
2003-12-02 1:59 ` cvs-commit at gcc dot gnu dot org
2003-12-02 2:00 ` zack at gcc dot gnu dot org
2003-12-02 2:03 ` pinskia at gcc dot gnu 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=20031202004529.5700.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).