Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: time to create the gdb-7.0.1 release (?)
Date: Mon, 21 Dec 2009 06:01:00 -0000	[thread overview]
Message-ID: <20091221060046.GX7752@adacore.com> (raw)
In-Reply-To: <20091219180214.GA13414@host0.dyn.jankratochvil.net>

Nice research work! 

I checked all the patches you proposed, except for one (see below).
I hesitated a bit on the dcache invalidate fix, but checked it in
in the end, mostly because of the symptoms (infinite loop). If we have
any problem with it, either 7.1 will soon be out, or I'll make an
emergency 7.0.2.

I did not see much point in regarding the testsuite patches, but checked
them in anyway, in case some people are in fact interested in the
testsuite results for the branch (I personally only follow the results
on the HEAD).

The patch that I did not commit was:

http://sourceware.org/ml/gdb-patches/2009-08/msg00448.html
http://sourceware.org/ml/gdb-cvs/2009-08/msg00139.html
Re: [patch] Support constant DW_AT_data_member_location by GCC PR debug/40659
        Support constant DW_AT_data_member_location by GCC PR debug/40659.
        * dwarf2read.c
        (dwarf2_add_field <DW_TAG_member> <DW_AT_data_member_location>):
        Initialize BYTE_OFFSET to 0 by default.  Explicitly check if
        attr_form_is_block.
        (dwarf2_add_field <DW_TAG_inheritance> <DW_AT_data_member_location>)
        (read_common_block <DW_AT_data_member_location>): New variable
        byte_offset.  Fix crash on non-DW_BLOCK ATTR values.
        Support constant DW_AT_data_member_location by GCC PR debug/40659.
        * gdb.dwarf2/dw2-inheritance.exp, gdb.dwarf2/dw2-inheritance.S: New.

As far as I can tell, this one is already in the branch (was checked
in before the branch got cut). Do you actually see a SEGV with gdb-7.0?
If yes, must be something else... Let me know, because I'd like to make
the release RSN.

-- 
Joel


  reply	other threads:[~2009-12-21  6:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  6:17 Joel Brobecker
2009-12-18  7:44 ` Ralf Corsepius
2009-12-18  8:10   ` Joel Brobecker
2009-12-18  8:52 ` Hui Zhu
2009-12-18  8:56   ` Joel Brobecker
2009-12-18  9:02     ` Hui Zhu
2009-12-18  9:45       ` Joel Brobecker
2009-12-18 14:24 ` Jack Howarth
2009-12-18 14:33   ` Joel Brobecker
2009-12-18 17:35 ` Michael Snyder
2009-12-18 17:40   ` Joel Brobecker
2009-12-18 17:54     ` Michael Snyder
2009-12-19 18:03 ` Jan Kratochvil
2009-12-21  6:01   ` Joel Brobecker [this message]
2009-12-21  9:07     ` Jan Kratochvil
2009-12-20 20:27 ` Jan Kratochvil
2009-12-21  9:54 ` Vladimir Prus

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=20091221060046.GX7752@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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