From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix flags type initialization bug
Date: Wed, 23 Aug 2006 17:38:00 -0000 [thread overview]
Message-ID: <20060823051122.GD1060@adacore.com> (raw)
In-Reply-To: <200608222104.k7ML4D0w031633@elgar.sibelius.xs4all.nl>
> > Is there a way to cause GDB 6.5 to crash, or is only after you
> > applied your changes?
>
> This is used in i386-tdep.c since january or so, and I think there is
> a risk of having it crash there, but I've never seen it happen.
If there is a risk, then let's apply the patch. Let me know if you'd
like me to do it. I have a check out of the branch already available,
so I can do it pretty efficiently.
> > Right now, I don't have any plan in making a minor release from
> > the 6.5 branch, but I don't mind making one if the fixes of this
> > kind keep piling up.
>
> This one alone isn't enough, but if there are a few others like it
> that can potentially crash gdb itself, I think we should consider
> having a 6.5.1 release.
You're no3 on the list of fixes that made it to the branch.
I try to be careful in my review of the patches that are applied,
so hopefully I didn't miss any. My idea was to make a 6.5.1 release
in october or november if I had enough patches. 3 could qualify as
enough. Maybe we'll have a couple more by then.
--
Joel
next prev parent reply other threads:[~2006-08-23 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 20:24 Mark Kettenis
2006-08-22 20:57 ` Joel Brobecker
2006-08-22 21:31 ` Mark Kettenis
2006-08-23 17:38 ` Joel Brobecker [this message]
2006-08-25 2:24 ` Mark Kettenis
2006-09-01 19:02 ` Joel Brobecker
2006-09-01 21:18 ` Mark Kettenis
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=20060823051122.GD1060@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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