Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/MI testsuite] gdb/701 test (varobj)
Date: Mon, 16 Sep 2002 11:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0209161156410.1395-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <3D8281AE.8090505@redhat.com>

On Fri, 13 Sep 2002, Fernando Nasser wrote:

> As you are at it, canyou take a look at this old patch of mine that I've 
> found lost in a branch....  Something should be broken without it!

I can take a look at it. It seems to me that this looks plausible. I'll 
see if I can add some more test which check the type-changing stuff. As I 
recall, we've historically had some problems with this code. Having a 
testcase should clear things up.

Keith



  reply	other threads:[~2002-09-16 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 16:49 Keith Seitz
2002-09-13 17:25 ` Fernando Nasser
2002-09-16 11:56   ` Keith Seitz [this message]
2002-09-17 12:24   ` Keith Seitz
2002-09-18  7:46     ` Fernando Nasser
2002-09-13 17:37 ` Andrew Cagney
2002-09-16 12:02   ` Keith Seitz

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=Pine.LNX.4.44.0209161156410.1395-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.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