Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: nickrob@snap.net.nz, mark.kettenis@xs4all.nl, ghost@cs.msu.su,
	        gdb-patches@sources.redhat.com
Subject: Re: MI failures related to string printing
Date: Wed, 17 Jan 2007 21:44:00 -0000	[thread overview]
Message-ID: <200701172144.l0HLiDuP001951@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070117060552.GC19331@nevyn.them.org> (message from Daniel 	Jacobowitz on Wed, 17 Jan 2007 01:05:52 -0500)

> Date: Wed, 17 Jan 2007 01:05:52 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, ghost@cs.msu.su,
>         gdb-patches@sources.redhat.com
> Mail-Followup-To: Nick Roberts <nickrob@snap.net.nz>,
> 	Mark Kettenis <mark.kettenis@xs4all.nl>, ghost@cs.msu.su,
> 	gdb-patches@sources.redhat.com
> Content-Disposition: inline
> X-XS4ALL-DNSBL-Checked: mxdrop9.xs4all.nl checked 66.93.172.17 against DNS blacklists
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0.0 () DK_POLICY_SIGNSOME
> X-XS4ALL-Spam: NO
> Envelope-To: mark.kettenis@xs4all.nl
> X-UIDL: 1169013955._smtp.mxdrop9.92459,S=2839
> 
> On Wed, Jan 17, 2007 at 10:45:47AM +1300, Nick Roberts wrote:
> > would have tried to adjust it.  When is it appropriate to use an XFAIL, if
> > not here?
> 
> XFAIL are expected failures due to limitations of the environment.
> Something which broke because your OS kernel version doesn't support
> it, or because no version of GCC emits good information, is a
> legitimate XFAIL.
> 
> >  > I'm still not convinced the change is ok.  Having 'char *' point to a
> >  > buffer that's not null-terminated is not uncommon.  We have a lot of
> >  > those in gdb itself.
> 
> Hi Mark,
> 
> We already use the equivalent of "print" to pass the value to the front
> end when it asks for the variable's value.  What Nick's change did was
> to use the same code when it asks if the variable's "value" has
> changed.  I think it's an improvement on that basis alone.
> 
> If we wanted printing a char * which doesn't point to a string to stop
> after one character, we'd need some way to identify strings, which
> C doesn't really give us.  As long as it's convenient for "print"
> to dump out the string, I suspect MI ought to too.

Agreed, at least if you explicitly ask for it.  However, the testsuite
does something like "-var-update *", which does not seem very explicit
to me.  Or am I missing something.

Mark


  reply	other threads:[~2007-01-17 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200701121351.29310.vladimir@codesourcery.com>
     [not found] ` <17831.31430.442855.801431@kahikatea.snap.net.nz>
2007-01-16  2:08   ` Vladimir Prus
2007-01-16  5:50     ` Nick Roberts
2007-01-16  6:42       ` Vladimir Prus
2007-01-16 20:44         ` Nick Roberts
2007-01-16 23:06           ` Vladimir Prus
2007-01-17  0:59             ` Nick Roberts
2007-01-17  6:01               ` Daniel Jacobowitz
2007-01-17  8:12                 ` Nick Roberts
2007-01-16 21:23       ` Mark Kettenis
2007-01-16 22:16         ` Nick Roberts
2007-01-17  6:06           ` Daniel Jacobowitz
2007-01-17 21:44             ` Mark Kettenis [this message]
2007-01-17 22:19               ` Daniel Jacobowitz

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=200701172144.l0HLiDuP001951@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=nickrob@snap.net.nz \
    /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