Re: [Rpcemu] rpcemu v01.5 - segmentationfault...

Hi David,

> https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide#Segmentation_faults
>
> and read about rdb and then ran the command. Here is the result of my
> attempt to do something correctly!

Yep, you did it right.

> (gdb) r
> Starting program: /home/zed/rpcemu-0.8.15/rpcemu
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7ffff4afc700 (LWP 21629)]
> [New Thread 0x7ffff41ed700 (LWP 21630)]
> [New Thread 0x7ffff28be700 (LWP 21631)]
> [New Thread 0x7ffff20bd700 (LWP 21632)]
> [New Thread 0x7fffe59ea700 (LWP 21633)]
> [Thread 0x7fffe59ea700 (LWP 21633) exited]
> [New Thread 0x7fffe59ea700 (LWP 21634)]
> [New Thread 0x7fffe4fe3700 (LWP 21635)]
>
> Thread 1 "rpcemu" received signal SIGSEGV, Segmentation fault.
> 0x00005555570becba in rcodeblock ()
> (gdb) bt full
> #0 0x00005555570becba in rcodeblock ()
> No symbol table info available.
> #1 0x00007fffffffdf70 in ?? ()
> No symbol table info available.
> #2 0x0000000000000000 in ?? ()
> No symbol table info available.
> (gdb)

I think this is saying the fault occurs in the generated-on-the-fly
machine code to emulate some ARM instructions, so I wouldn't expect that
next section on "more detail" to help.

https://marutan.net/rpcemu/linuxcompile.html has a note at the start
about Ubuntu 16.10 needing CFLAGS=-no-pie. I suspect this may now be
true of Debian also. So try that, going back to the configure stage.

--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu