question about Region_map::Region_conflict in attach_at()

[Alexander Tormasov]

Hello Christian, thank you for answer!

current map show
[init -> gdb_monitor -> mmaptest]   0x40000000 .. 0x4fffffff: stack area
[init -> gdb_monitor -> mmaptest]   0x30000 .. 0x1befff: ld.lib.so
[init -> gdb_monitor -> mmaptest]   0x10d55000 .. 0x10ffffff: libc.lib.so
[init -> gdb_monitor -> mmaptest]   0x10c3a000 .. 0x10d54fff: vfs.lib.so
[init -> gdb_monitor -> mmaptest]   0x10bee000 .. 0x10c39fff: libm.lib.so
[init -> gdb_monitor -> mmaptest]   0x1030000 .. 0x124bfff: stdcxx.lib.so
so, requested range 0x102e000 till 0x102f000 which is BEFORE allocated address related to stdcxx?

I assume that range could be free… while may be it is in use by heap/etc.

anyway, are there ANY way to check what particular addresses are in use, or at least, setup break in GDB to the place where this address generate Regionmap conflict?
where are the related places in the genode code?

If I will try to use Libc::valid(addr_t addr) - to verify that it is used, is it always give me correct results?

Sincerely,
	Alexander


> Sorry,
> 
> my last tip will not help you further. Now I remember that the region
> that conflicts with your attachment attempt at 0x102e000 is the linker
> area, which comprises 256 MiB beginning at the binary link address.
> 
> Christian
> 
> On Mon, Nov 16, 2020 at 08:49:03 CET, Christian Helmuth wrote:
>> Hello Alexander,
>> 
>> you enabled 'ld_verbose' in your configuration. Please check if
>> 0x102e000 is already used by any shared library. You may also check
>> the binary with 'genode-x86-readelf -l build/x86_64/debug/test-log'.