Debugging without GDB - stack print?

Alexander Tormasov a.tormasov at
Fri Aug 23 22:07:54 CEST 2019

Thank you for information!

Dump of my file show
Program Header:
    PHDR off    0x0000000000000040 vaddr 0x0000000000200040 paddr 0x0000000000000000 align 2**3
         filesz 0x0000000000000150 memsz 0x0000000000000150 flags r--
  INTERP off    0x000000000012bee2 vaddr 0x000000000112aee2 paddr 0x000000000112aee2 align 2**0
         filesz 0x000000000000000a memsz 0x000000000000000a flags r--
    LOAD off    0x0000000000001000 vaddr 0x0000000001000000 paddr 0x0000000001000000 align 2**12
         filesz 0x000000000015c9fc memsz 0x000000000015c9fc flags r-x
    LOAD off    0x000000000015e000 vaddr 0x000000000115d000 paddr 0x000000000115d000 align 2**12
         filesz 0x0000000000081e9c memsz 0x00000000001112f4 flags rw-
 DYNAMIC off    0x00000000001c0c18 vaddr 0x00000000011bfc18 paddr 0x00000000011bfc18 align 2**5
         filesz 0x000000000001f284 memsz 0x000000000001f26c flags rw-
EH_FRAME off    0x0000000000156030 vaddr 0x0000000001155030 paddr 0x0000000001155030 align 2**2
         filesz 0x00000000000079cc memsz 0x00000000000079cc flags r--
Does it mean that real offset in code is 
>>  ip=0xa95b1- 0x1000 
like 0xa85b1
Disassembly shows the following:
 10a85b1:       8b 15 69 85 11 00       mov    0x118569(%rip),%edx        # 11c0b20 <genode_argv+0x260>

Seems that argv is damaged…
While I still try to find exactly which function fail here

> 23 авг. 2019 г., в 22:26, ttcoder at написал(а):
> Hi Alexander,
>> ^Mno RM attachment (READ pf_addr=0x0 pf_ip=0xa95b1 from pager_object: 
>> pd='init -> noux -> test-go' thread='ep') 
>> ^MWarning: invalid signal-context capability
>> ^MWarning: page-fault, pager_object: pd='init -> noux -> test-go' 
>> thread='ep' ip=0xa95b1 pf-addr=0x0
>> Where I can find a map of load of my application? And symbols?
>> I found only something like test-go file, which I can read using readelf 
>> -s…
>> How to correspond pf_ip=0xa95b1 dress with code?
> I'm relatively new to Genode too, and try to collect responses to questions like those; mostly for my sake, but might be useful to you too; see Section 2 "Mapping the address to source code and function names" here:

More information about the users mailing list