Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.0 regressions: s390(x)-linux, ppc(64)-linux, spu-elf
Date: Mon, 28 Sep 2009 18:23:00 -0000	[thread overview]
Message-ID: <20090928182332.GJ9019@adacore.com> (raw)
In-Reply-To: <200909281632.n8SGW1YR004895@d12av02.megacenter.de.ibm.com>

I was going to reply again to your initial email, going through each
patch one by one, but since I already commented on some of the patches
directly on gdb-patches, I'll reply to this message instead.

> - Put in the patches that are testsuite-only (7, 8, 9 in my list)
>   They should be harmless and significantly clean up test suite
>   results on some platforms

Yeah, I agree.

> - Put in the solely platform-specific patches (3, 5, 6)
>   I've tested these, and they definitely help on those platforms

  3. Displaced stepping missing on S/390
     This one seems safe. At worst, non-stop would still be broken...

  5. PIE detection not enabled on PowerPC and S/390
     I suggested we pass on this one because it's just a missing warning.
     But it only affects the targets that you know much better than
     I do, so I'll trust your judgement on this one.

  6. SPU gdbserver regressions when killing inferior
     Agreed that it would be nice to have it for 7.0.

> - The bitfield regression (1) seems a serious error affecting
>   multiple platforms that really should be fixed, and the patch
>   seems straightforward ...

I think it's OK to put this in 7.0 as well. Daniel reviewed
your patch, so that's two pairs of eyes.

> - The displaced stepping regression is unfortunate, as it completely
>   breaks a new feature.  The patch *should* affect only PowerPC, but
>   it does need to touch generic files (infrun.c), so there's always
>   some risk.  In any case, I'd prefer to get at least some feedback
>   before putting it in ...

This one seems a little more problematic indeed. Is that a regression
compared to 6.8? If it is, perhaps we could try to get it fixed for
7.0.1 instead?

> - The Obj-C changes are not really a regression, so it may not really
>   be critical to put those in.  On the other hand, they just touch
>   Obj-C code (except for one PowerPC-specific bugfix), and they 
>   drastically improve the situation on PowerPC-64, so it would be
>   nice ...  Again, I'd definitely like some feedback first.

Given the severity of the problem (SEGV), I think we should put your
patch in 7.0.

-- 
Joel


  reply	other threads:[~2009-09-28 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 21:55 Ulrich Weigand
2009-09-28 15:38 ` Joel Brobecker
2009-09-28 16:32   ` Ulrich Weigand
2009-09-28 18:23     ` Joel Brobecker [this message]
2009-09-29  1:05       ` Ulrich Weigand
2009-09-29  1:39         ` Joel Brobecker
2009-09-29 12:55           ` Ulrich Weigand
2009-09-28 16:41 ` Tom Tromey

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=20090928182332.GJ9019@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.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