unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 37231@debbugs.gnu.org
Subject: bug#37231: 27.0.50; concurrent XML validation yields an invalid file
Date: Fri, 20 Sep 2019 20:53:05 +0200	[thread overview]
Message-ID: <87d0fu94vi.fsf@gnus.org> (raw)
In-Reply-To: <87r253m7xu.fsf@vinc17.net> (Vincent Lefevre's message of "Fri, 30 Aug 2019 09:25:01 +0200")

Vincent Lefevre <vincent@vinc17.net> writes:

> Consider a big, valid XML file a.xml, e.g. using a vacuous schema, and
> copy it to b.xml (thus a.xml and b.xml are the same file, though they
> don't need to be identical for the test).
>
> Open the files at the same time with: emacs -Q a.xml b.xml
>
> Then one of them is regarded as invalid.

I can confirm that this bugs out.

I know nothing about the nxml code, but I did notice that about half of
the rng variables are defined thusly:

(defvar rng-validate-up-to-date-end nil
  "Last position where validation is known to be up to date.")
(make-variable-buffer-local 'rng-validate-up-to-date-end)

But the ones that it reports as failing here depends on variables like
`rng-pending-contents', which are not buffer-local.  So to test blindly,
I made that also buffer-local...  and then the entire process failed
with a backtrace, so that's not the solution.  :-)

But I do think it's really suspicious that some of those variables are
buffer-local while others aren't.  Perhaps somebody who knows how that
machinery works could have a peek at it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-09-20 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  7:25 bug#37231: 27.0.50; concurrent XML validation yields an invalid file Vincent Lefevre
2019-09-20 18:53 ` Lars Ingebrigtsen [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0fu94vi.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37231@debbugs.gnu.org \
    --cc=vincent@vinc17.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).