From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Fix issues with gdb-memory-map.dtd
Date: Fri, 24 Nov 2017 21:35:00 -0000 [thread overview]
Message-ID: <8f8c59499450f4d4972530cd5c0e070a@polymtl.ca> (raw)
In-Reply-To: <20171124213020.kskjia7qr55473zf@adacore.com>
On 2017-11-24 16:30, Joel Brobecker wrote:
>> You are probably the person that has the most chance to know how to
>> update this file:
>>
>> http://sourceware.org/gdb/gdb-memory-map.dtd
>>
>> Any idea?
>
> I can absolutely do that. But I'm wondering whether we might
> just want to delete the file instead? Why keep a copy on
> the website? I couldn't find a reference to it anywhere
> in any of the webpages...
The XML files that follow this dtd can point to it. For example, look
at the example in the doc:
https://sourceware.org/gdb/onlinedocs/gdb/Memory-Map-Format.html
This allows a tool to validate that the XML respects the dtd, and XML
editors can provide assistance when hand-writing it, giving
auto-complete based on the possible options.
Simon
next prev parent reply other threads:[~2017-11-24 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 23:18 Simon Marchi
2017-11-09 23:18 ` [PATCH 2/2] Fix mem region parsing regression and add test Simon Marchi
2017-11-14 21:43 ` Simon Marchi
2017-11-10 8:01 ` [PATCH 1/2] Fix issues with gdb-memory-map.dtd Eli Zaretskii
2017-11-10 21:01 ` Simon Marchi
2017-11-24 16:31 ` Simon Marchi
2017-11-24 21:30 ` Joel Brobecker
2017-11-24 21:35 ` Simon Marchi [this message]
2017-11-24 21:57 ` Joel Brobecker
2017-11-24 22:15 ` Simon Marchi
2017-11-24 22:23 ` Joel Brobecker
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=8f8c59499450f4d4972530cd5c0e070a@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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