depot_query: segmentation in _query_blueprint?

[Norman Feske]

Hi Roman,

> There's no segfault if I either completely remove the empty
> `<config/>`-node or replace it with `<config></config>`.
> 
> For me it looks like [1] refers to a similar issue in a different context.
> 
> [1] https://lists.genode.org/pipermail/users/2019-June/006781.html

intuitively, this looks related, indeed. But given the code, I'm unable
to immediately spot the same pattern. The '_apply_blueprint' does not
parse the <config> node after all. It merely copies the compounding
<runtime> node as is (via 'Xml_node::with_raw_node').

I just tried to reproduce the problem by executing the depot_query.run
script (modified to deploy chroot) for NOVA on x86_32 and base-hw on
pbxa9 (ARM) but I could not trigger it.

Do you have an example scenario that I could use for reproducing the
problem at hand? I'd very much appreciate that.

You left a few of my questions unanswered. In particular,

* Does the problem occur on any kernel/architecture combination
  other than base-linux on 32-bit ARM?

* Does it occur when using the original tool chain?

Cheers
Norman

-- 
Dr.-Ing. Norman Feske
Genode Labs

https://www.genode-labs.com · https://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth