how to debug gdb?

Alexander Tormasov a.tormasov at innopolis.ru
Sun Apr 11 00:03:50 CEST 2021


I try to start linux version and fail
...
  Program lib/ld/linux/ld-linux
make[1]: Leaving directory '/var/services/homes/admin/gen/21.02/build/x86_64'
genode build completed
using 'core-linux' as 'core'
using 'linux_timer_drv' as 'timer'
using 'ld-linux.lib.so' as 'ld.lib.so'
spawn ./core
Genode 20.11-203-g9c8a05c12 <local changes>
17592186044415 MiB RAM and 8997 caps assigned to init
[init] Error: SECCOMP_SET_MODE_FILTER failed -38
[init] Error: Uncaught exception of type 'Genode::Exception'
[init] Warning: abort called - thread: ep

> 9 апр. 2021 г., в 14:45, Norman Feske <norman.feske at genode-labs.com> написал(а):
> 
> Hi Alexander,
> 
> On 08.04.21 19:42, Alexander Tormasov via users wrote:
>> I try to run it via gdb, using the following run file attached below (which works in the past).
> 
> I wonder, have you considered debugging such issues on base-linux as
> described here?
> 
>  https://genodians.org/ssumpf/2019-04-26-java-gdb
> 
> At least that is my time-tested work flow when working on any regular
> component or protocol stack, including low-level code like the dynamic
> linker, libc, vfs, etc.

I suspect that I need low level memory handling functions like mmap/vfork/etc

not sure for 100% that linux version support them



More information about the users mailing list