[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1221966
Title:
SIGSEGV in
Also I just noticed that the original report says the crash is while
trying to run a SunOS binary. This isn't supported at all -- we can run
Linux Sparc binaries with qemu-sparc, not random-other-OS binaries, and
"guest binary crashes" is not an implausible result...
--
You received this bug noti
Triaging old bug tickets ... is this still an issue with the latest
version of QEMU or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://
And, in the grand scheme of things, I've been trying to piece together
what the problem software is that I need qemu for. It turns out I've
got two very old sparcs both running Oracle with a variety of client
programs I need. It could be that qemu-sparc is a waste of time and I
need to focus on q
Oh is it? Sorry, I guess I didn't understand what that function was
doing. That thing is sort of confusing in there...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1221966
Title:
SIGSEGV in stat
"it is qemu segfaulting when it tries to generate the code buffer" --
why do you think this? The backtrace you quote shows the segfault inside
static_code_gen_buffer(), which means we are running the generated code,
not doing codegen.
--
You received this bug notification because you are a member
If I run it normally, it crashes in the same way. If I pass the signal
through it crashes in the same way. I sort of expect this, since it is
qemu segfaulting when it tries to generate the code buffer, not the
underlying problem.
--
You received this bug notification because you are a member of
SIGSEGVs from qemu-linux-user are expected -- this is how we track self-
modifying code in the guest binary. We catch the SIGSEGV and handle it
appropriately. In particular, SPARC binaries do this a lot because their
dynamic-linking mechanism involves self-modifying code.
If you don't run the prog
