On 14 January 2016 at 13:50, Franz-Josef Haider
wrote:
> This would be a unstripped version of the qemu-i386 binary:
> https://www.dropbox.com/s/s9f8pcn5co34khn/qemu-i386?dl=0, although i think
> it is not worth trying to pursue this any further, because i have updated
> GCC in my build chroot (sc
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 binary you provide
On 22 December 2015 at 21:37, Franz-Josef Haider
wrote:
> https://www.dropbox.com/s/vh2efuulpk89s23/sarge.tar.gz?dl=0
>
> This is a sarge installation. Executing apt-get update triggers the crash
> for me. I understand that the commit i referenced earlier is probably not
> the root cause, but i ve
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 been able to reproduce
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 been able to reproduce
any of these crashes or lockups I'm getting
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 problem I thou
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 under qem
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 under qemu, adding
>>>-D qemu.log -d in_
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,exec,i
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,exec,int,cpu,guest_errors,unimp
>> on the com
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 thr
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 thread
> Id Target Id Fram
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/bin.IBM_
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/bin.IBM_INTEL_LINUX]LD_LIBRARY_PATH=/home/user/
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 18 November 2015 at 16:33, Franz-Josef Haider
wrote:
> sure, apt-get:
>
> root@Nokia-N900:/# gdb apt-get qemu_apt-get_20151118-120024_16081.core
> GNU gdb 6.3-debian
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
>
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 si
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 signal 11 (Segmentation fault) -
18 matches
Mail list logo
