Hi!
Commit 9f08c8ec73878122ad4b061ed334f0437afaaa32 breaks qemu i386 user
mode emulation for me (on arm):
[1|user@Nokia-N900|~]/home/user/MyDocs/maple13_i386/bin/start_cmaple.sh
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/home/user/MyDocs/maple13_i386/bin/start_cmaple.s
On 11/18/2015 03:56 PM, Eric Blake wrote:
On 11/18/2015 05:27 AM, Franz-Josef Haider wrote:
Hi!
Commit 9f08c8ec73878122ad4b061ed334f0437afaaa32 breaks qemu i386 user
mode emulation for me (on arm):
[1|user@Nokia-N900|~]/home/user/MyDocs/maple13_i386/bin/start_cmaple.sh
qemu: uncaught target
On 11/18/2015 01:27 PM, Franz-Josef Haider wrote:
Hi!
Commit 9f08c8ec73878122ad4b061ed334f0437afaaa32 breaks qemu i386 user
mode emulation for me (on arm):
[1|user@Nokia-N900|~]/home/user/MyDocs/maple13_i386/bin/start_cmaple.sh
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
On 11/23/2015 10:51 PM, Peter Maydell wrote:
On 23 November 2015 at 17:50, Franz-Josef Haider
wrote:
But this is a backtrace from directly launching cmaple.
# qemu configure line: ./configure --prefix=/usr --static
--target-list=i386-linux-user
[1|user@Nokia-N900|~/MyDocs/maple13_i386
On 11/24/2015 10:08 AM, Peter Maydell wrote:
On 24 November 2015 at 07:28, Franz-Josef Haider
wrote:
On 11/23/2015 10:51 PM, Peter Maydell wrote:
(gdb) run cmaple
Starting program: /usr/bin/qemu-i386 cmaple
Program received signal SIGSEGV, Segmentation fault.
0x600104c0 in ?? ()
(gdb) info
On 11/27/2015 03:31 PM, Peter Maydell wrote:
On 24 November 2015 at 10:19, Franz-Josef Haider
wrote:
On 11/24/2015 10:08 AM, Peter Maydell wrote:
OK, that's definitely not the problem I thought it might have been.
Can you run maple under qemu, adding
-D qemu.log -d in_asm,out_asm,op
On 12/01/2015 05:47 PM, Peter Maydell wrote:
On 27 November 2015 at 14:31, Peter Maydell wrote:
On 24 November 2015 at 10:19, Franz-Josef Haider
wrote:
On 11/24/2015 10:08 AM, Peter Maydell wrote:
OK, that's definitely not the problem I thought it might have been.
Can you run maple
On 12/08/2015 10:01 PM, Franz-Josef Haider wrote:
On 12/01/2015 05:47 PM, Peter Maydell wrote:
On 27 November 2015 at 14:31, Peter Maydell
wrote:
On 24 November 2015 at 10:19, Franz-Josef Haider
wrote:
On 11/24/2015 10:08 AM, Peter Maydell wrote:
OK, that's definitely not the prob
On 12/22/2015 01:16 PM, Peter Maydell wrote:
On 18 December 2015 at 19:03, Franz-Josef Haider
wrote:
Hi, i don't know why it locked up previously with a fresh clone it does not
lock up anymore, but it still crashes with current master.
Hmm. Unfortunately since I haven't be
On 01/07/2016 08:18 PM, Peter Maydell wrote:
On 22 December 2015 at 21:37, Franz-Josef Haider
wrote:
This is a sarge installation. Executing apt-get update triggers the crash
for me.
OK, I've now been able to try that on my hardware.
(1) If I use your chroot, and the qemu binar
10 matches
Mail list logo
