Hi Genodians,
I'm trying to run a noux in a dynamic init, whereby I'm getting a Region Conflict exception from LD. I have no idea what's causing that.
[init -> dynamic -> noux] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' [init -> dynamic -> noux] Error: Uncaught exception of type 'Genode::Region_map::Region_conflict' [init -> dynamic -> noux] Warning: abort called - thread: ep [init -> dynamic] child "noux" exited with exit value 1
Can someone please point me where to look for the cause?
Bests Stefan
Hi Stefan,
Could you provide more information about what you're trying to do? On which kernel, on which platform, which version of Genode, at best a run script that allows us to reproduce the problem.
Cheers, Martin
El 26/3/19 a las 10:12, Stefan Thöni escribió:
Hi Genodians,
I'm trying to run a noux in a dynamic init, whereby I'm getting a Region Conflict exception from LD. I have no idea what's causing that.
[init -> dynamic -> noux] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' [init -> dynamic -> noux] Error: Uncaught exception of type 'Genode::Region_map::Region_conflict' [init -> dynamic -> noux] Warning: abort called - thread: ep [init -> dynamic] child "noux" exited with exit value 1
Can someone please point me where to look for the cause?
... If you rather like to investigate yourself: the problem seems to occur while the dynamic linker is mapping the program binary and its dependencies. You may want to have a look at Component::construct in base/src/lib/ldso/main.cc and find out which mapping fails and which is the other mapping that already occupies the desired region.
Cheers, Martin
El 26/3/19 a las 11:07, Martin Stein escribió:
Hi Stefan,
Could you provide more information about what you're trying to do? On which kernel, on which platform, which version of Genode, at best a run script that allows us to reproduce the problem.
Cheers, Martin
On 26.03.19 11:18, Martin Stein wrote:
... If you rather like to investigate yourself: the problem seems to occur while the dynamic linker is mapping the program binary and its dependencies. You may want to have a look at Component::construct in base/src/lib/ldso/main.cc and find out which mapping fails and which is the other mapping that already occupies the desired region.
Thanks, that helped me find it. Turns out I misspelled a route and loaded ld.lib.so twice.
Bests Stefan
-
Martin Stein -
Stefan Thöni