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

[Ralph Corderoy]

Hi David,
> > > zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15/src CFLAGS=-no-pie
> > > ./configure --enable-dynarec
> >
> > You've glued two separate commands together here.
> >
> > First do this: cd /home/zed/rpcemu-0.8.15/src
> >
> > Then do this: CFLAGS=-no-pie ./configure --enable-dynarec
>
> Thanks for your response.  By now my email of 13 August will have reached
> the rpcemu mailing list and you will see that David Pitt's suggestion
> worked.

Yes, but we're trying to explain what you did wrong so you know for next
time.  Especially as you didn't merge the two commands when you
initially successfully got it to configure before asking the list for
help so it seems odd to merge them afterwards.

You were doing the equivalent of

*Dir $.home.zed.rpcemu-0.8.15.src
*Run configure

as

*Dir $.home.zed.rpcemu-0.8.15.src Run configure

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

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

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

[zed]

Hi David


David Glover-Aoki  wrote:

> On Aug 12, 2017, at 8:25 PM, zed  wrote:
> > 
> > zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15/src CFLAGS=-no-pie
> > ./configure --enable-dynarec
> 
> You've glued two separate commands together here.
> 
> First do this: cd /home/zed/rpcemu-0.8.15/src
> 
> Then do this: CFLAGS=-no-pie ./configure --enable-dynarec
> 

Thanks for your response.  By now my email of 13 August will have reached
the rpcemu mailing list and you will see that David Pitt's suggestion
worked.  

David
-- 
zed
Despite the high cost of living, it remains popular  


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

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

[David Glover-Aoki]

On Aug 12, 2017, at 8:25 PM, zed  wrote:
> 
> zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15/src CFLAGS=-no-pie ./configure
> --enable-dynarec

You've glued two separate commands together here.

First do this:
cd /home/zed/rpcemu-0.8.15/src

Then do this:
CFLAGS=-no-pie ./configure --enable-dynarec

-- 
David Glover-Aoki
https://david.gloveraoki.net/contact


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

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

[Ralph Corderoy]

Hi David,

> > 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.
> 
> Went to the website suggested and did as suggested (CFLAGS=-no-pie
> ./configure --enable-dynarec --enable-debug) and got a response
> too many arguments
> but unfortunately did not save the output.

That response doesn't make a lot of sense, unless you're using some
weird shell.  Does `echo $BASH_VERSION' display a useful
version-number-ish value?

> I then tried without the configuration options (i.e. just the
> CFLAGS=-no-pie)

That would just set a variable in your shell.  Not an error, but no
desired effect.

> I then started again and got the following output
> 
> zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15
> zed@zed-pc:~/rpcemu-0.8.15$ CFLAGS=-no-pie ./configure --enable-dynarec 
> --enable-debug
> bash: ./configure: No such file or directory

Yes, start again.  You said at
http://www.riscos.info/pipermail/rpcemu/2017-August/002526.html that you
configured it just fine.  You need to repeat that, but with
`CFLAGS=-no-pie' as a word before the ./configure.

When you're entering `./configure' you are asking to run the file
configure in the current directory, `.'.  So a plain `ls' should show
the current directory's contents, including configure.

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

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

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

[zed]

Hi Ralph


Ralph Corderoy  wrote:

> 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.

Thank goodness for that!
 
[snip]
> > Thread 1 "rpcemu" received signal SIGSEGV, Segmentation fault.
> > 0x570becba in rcodeblock () (gdb) bt full #0
> > 0x570becba in rcodeblock () No symbol table info available. #1
> > 0x7fffdf70 in ?? () No symbol table info available. #2
> > 0x 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.

Went to the website suggested and did as suggested (CFLAGS=-no-pie
./configure --enable-dynarec --enable-debug)and got a response

too many arguments

but unfortunately did not save the output.

I then tried without the configuration options (i.e. just the
CFLAGS=-no-pie) and was returned to

zed@zed-pc:~/rpcemu-0.8.15$ CFLAGS=-no-pie

I then started again and got the following output

zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15
zed@zed-pc:~/rpcemu-0.8.15$ CFLAGS=-no-pie ./configure --enable-dynarec
--enable-debug
bash: ./configure: No such file or directory
zed@zed-pc:~/rpcemu-0.8.15$ ./configure --enable-dynarec --enable-debug
bash: ./configure: No such file or directory
zed@zed-pc:~/rpcemu-0.8.15$ 

Would the fact that I did 

zed@zed-pc:~/rpcemu-0.8.15$ CFLAGS=-no-pie

have led to the output of No such file or directory?

I have checked and found that doing a cd  works on every
other Directory I've tried, other than /rpcemu-0.8.15 one.

As an aside, I have Linux Mint v18.2 Mate installed in another partition.
I booted into this and had no difficulty in installing rpcemu-0.8.15,
other than that the window which opened was very small and I could not
adjust it and there was only one screen resolution available.  I was able
to run !Draw and Paint! without problem, but could not open a floppy disc
containing !Drawfiles.  Just got an error asking whether the disc was
formatted!  That could be because when I upgraded this desktop a few years
ago, I've never checked whether the floppy disc drive was connected.

Again, thank you for staying with this.  All suggestions welcome.

Regards

David


-- 
zed
A friendly" program doesn't have a 600 page manual! 


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

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

[Ralph Corderoy]

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 0x74afc700 (LWP 21629)]
> [New Thread 0x741ed700 (LWP 21630)]
> [New Thread 0x728be700 (LWP 21631)]
> [New Thread 0x720bd700 (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.
> 0x570becba in rcodeblock ()
> (gdb) bt full
> #0  0x570becba in rcodeblock ()
> No symbol table info available.
> #1  0x7fffdf70 in ?? ()
> No symbol table info available.
> #2  0x 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

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

[zed]

Ralph Corderoy  wrote:

> Hi David,
> 
> > $ ./rpcemu Shutting down Allegro due to signal #11 Segmentation fault
> > $
> 
>
https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide#Segmentation_faults
> shows how to `bt full' since it seems you're not used to gdb(1).  That
> gives us the first clue what might be going on.

Hi Ralph

Thank you for your very prompt reply.

I visited
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!

Terminal output

zed@zed-pc:~$ cd /home/zed/rpcemu-0.8.15
zed@zed-pc:~/rpcemu-0.8.15$ gdb ./rpcemu
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./rpcemu...done.
(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 0x74afc700 (LWP 21629)]
[New Thread 0x741ed700 (LWP 21630)]
[New Thread 0x728be700 (LWP 21631)]
[New Thread 0x720bd700 (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.
0x570becba in rcodeblock ()
(gdb) bt full
#0  0x570becba in rcodeblock ()
No symbol table info available.
#1  0x7fffdf70 in ?? ()
No symbol table info available.
#2  0x in ?? ()
No symbol table info available.
(gdb) 
 -
which means nothing whatsoever to me - way beyond my paygrade!

Neither did I understand the instructions which followed "Improved gdb
output" on the website, so seek your further assistance, please?

I have three allegro packages installed: 
libjpgallwegro4.4 v2.2.2.2-10
liballegro4-dev v2.4.4.2-10
liballegro4.4 v2.4.4.2-10

David

-- 
zed
CURSOR: An expert in four-letter words.


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

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

[Ralph Corderoy]

Hi David,

> $ ./rpcemu
> Shutting down Allegro due to signal #11
> Segmentation fault
> $

https://wiki.archlinux.org/index.php/Step-by-step_debugging_guide#Segmentation_faults
shows how to `bt full' since it seems you're not used to gdb(1).  That
gives us the first clue what might be going on.

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

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