public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] gdbserver <library-list> and its #FIXED version="1.0"
Date: Wed, 10 Jun 2015 16:17:00 -0000	[thread overview]
Message-ID: <55786327.9060002@redhat.com> (raw)
In-Reply-To: <20111103191640.GA27298@host1.jankratochvil.net>

On 11/03/2011 07:16 PM, Jan Kratochvil wrote:

> I believe the same bug has to apply for existing FSF gdbserver but I do not
> have any <library-list/> platform to test it (I did not try to build MinGW).
> 
> features/library-list.dtd:
> <!ATTLIST library-list  version CDATA   #FIXED  "1.0">
> 
> http://www.xml.com/pub/a/98/10/guide0.html?page=3 says:
> 
> #FIXED
> 	In this case, the attribute is not required, but if it occurs, it must
> 	have the specified value.
> 
> Which would suggest gdbserver is right but solib-target.c is wrong.  One could
> also make gdbserver explicit for the version (if those 14 bytes are not of
> a concern).

Yeah, I couldn't find any other place that handled "version"
optionally.  Looking around, it looks like we end up passing
an explicit version number for all xml files but this one.

> +  /* #FIXED attribute may be omitted, Expat returns NULL in such case.  */
> +  if (version)

version != NULL

Otherwise looks fine.

Thanks,
Pedro Alves

      parent reply	other threads:[~2015-06-10 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 19:17 Jan Kratochvil
2015-06-07 14:11 ` ping: " Jan Kratochvil
2015-06-08  9:08   ` Gary Benson
2015-06-10 16:31     ` [commit] " Jan Kratochvil
2015-06-10 17:38       ` [commit#2] " Jan Kratochvil
2015-06-10 16:17 ` Pedro Alves [this message]

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=55786327.9060002@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).