Am 20.08.2018 um 22:39 schrieb Howard Spoelstra:
> Confirmed, adding --disable-stack-protector to configure results in a
> working binary.
>
> Great, thanks,
> Howard
There is already a bug report for gcc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832
It looks like not only Windows but also
On Mon, Aug 20, 2018 at 9:47 PM, Stefan Weil wrote:
> Am 20.08.2018 um 21:41 schrieb Stefan Weil:
>> That's a problem triggered by gcc 8 for Mingw-w64 with compiler options
>> -fstack-protector-all and -fstack-protector-strong. With any of those
>> options this simple test program also fails with
Am 20.08.2018 um 21:41 schrieb Stefan Weil:
> That's a problem triggered by gcc 8 for Mingw-w64 with compiler options
> -fstack-protector-all and -fstack-protector-strong. With any of those
> options this simple test program also fails with SIGSEGV:
>
> #include
> int main(void) {
> SYSTEM_INFO
> Am 18.07.2018 um 08:33 schrieb Howard Spoelstra:
> [...]> Issue 2: once strncpy has been replaced with memcpy in these two
>> instances, I can successfully compile, but the executable doesn't run
>> in Windows.
>> I tried to debug, and this is what gdb told me:
>>
>> (gdb) run
>> Starting program
Am 18.07.2018 um 08:33 schrieb Howard Spoelstra:
[...]> Issue 2: once strncpy has been replaced with memcpy in these two
> instances, I can successfully compile, but the executable doesn't run
> in Windows.
> I tried to debug, and this is what gdb told me:
>
> (gdb) run
> Starting program: c:\qemu
Am 18.08.2018 um 22:51 schrieb Howard Spoelstra:
> On Sat, Aug 18, 2018 at 9:09 PM, Stefan Weil wrote:
>> Am 17.08.2018 um 09:32 schrieb David Hildenbrand:
>>> No being a win32/mingw expert, Stefan any idea?
>>
>>
>> I'd try a debug build (configure [...] --enable-debug).
>>
>> My installers (http
I'm also seeing this behaviour using the MSYS2 packaged mingw64 compiler, GCC
8.2. I have managed to cross compile QEMU successfully under Fedora 28 however
and the resulting binary works. Certainly seems like a tool chain issue,
unfortunately MSYS2 doesn't package any older versions of GCC.
Be
On Sat, Aug 18, 2018 at 9:09 PM, Stefan Weil wrote:
> Am 17.08.2018 um 09:32 schrieb David Hildenbrand:
>> On 18.07.2018 08:33, Howard Spoelstra wrote:
>>> Hi all,
>>>
>>> I have two issues when cross compiling current master for Windows with
>>> mingw 8.1. Host is Fedora29. See further below for
Hi,
On 08/18/2018 04:09 PM, Stefan Weil wrote:
> Am 17.08.2018 um 09:32 schrieb David Hildenbrand:
>> On 18.07.2018 08:33, Howard Spoelstra wrote:
>>> Hi all,
>>>
>>> I have two issues when cross compiling current master for Windows with
>>> mingw 8.1. Host is Fedora29. See further below for gcc a
Am 17.08.2018 um 09:32 schrieb David Hildenbrand:
> On 18.07.2018 08:33, Howard Spoelstra wrote:
>> Hi all,
>>
>> I have two issues when cross compiling current master for Windows with
>> mingw 8.1. Host is Fedora29. See further below for gcc and mingw
>> versions.
>>
>> Reproduce with:
>> ./config
On Fri, Aug 17, 2018 at 9:32 AM, David Hildenbrand wrote:
> On 18.07.2018 08:33, Howard Spoelstra wrote:
>> Hi all,
>>
>> I have two issues when cross compiling current master for Windows with
>> mingw 8.1. Host is Fedora29. See further below for gcc and mingw
>> versions.
>>
>> Reproduce with:
>>
On 18.07.2018 08:33, Howard Spoelstra wrote:
> Hi all,
>
> I have two issues when cross compiling current master for Windows with
> mingw 8.1. Host is Fedora29. See further below for gcc and mingw
> versions.
>
> Reproduce with:
> ./configure --cross-prefix=x86_64-w64-mingw32-
> --target-list="pp
Hi all,
I have two issues when cross compiling current master for Windows with
mingw 8.1. Host is Fedora29. See further below for gcc and mingw
versions.
Reproduce with:
./configure --cross-prefix=x86_64-w64-mingw32-
--target-list="ppc-softmmu" --enable-gtk --with-gtkabi=3.0
--enable-sdl --with-s
Hi,
Below are bugs filed in this week for Upstream qemu and libvirt:
Qemu in Launchpad:
https://bugs.launchpad.net/opensuse/+bug/1199416
Hot-add qcow2 [virtio-scsi] devices doesn't work in SlLES-11-SP2guest
Libvirt Bugs:
Bug 982224 - Attaching of the Virtio-scsi [qcow2] drives fails with
"er
Am 19.02.2011 17:21, schrieb Stefan Hajnoczi:
On Sat, Feb 19, 2011 at 12:27 PM, Chunqiang Tang wrote:
I applied FVD's fully automated testing tool to the VDI block device
driver and found several bugs. Some bugs are easy to fix whereas others
need some thoughts on design. Therefore, I thought y
On Sat, Feb 19, 2011 at 12:27 PM, Chunqiang Tang wrote:
> I applied FVD's fully automated testing tool to the VDI block device
> driver and found several bugs. Some bugs are easy to fix whereas others
> need some thoughts on design. Therefore, I thought you might be able to
> handle the bugs bette
Hi Stefan,
I applied FVD's fully automated testing tool to the VDI block device
driver and found several bugs. Some bugs are easy to fix whereas others
need some thoughts on design. Therefore, I thought you might be able to
handle the bugs better than me. These bugs occur only if I/O errors or
Hi,
my migration issues currently look like they are driven by at least two
bugs (that's real fun). One slipped into qemu-kvm during merge of
upstream, the other is either an issue of current kvm.git master or
kvm-kmod's wrapping of the latter.
Problem 1
-
Setup: qemu-kvm after 249cdd049c
On 3/31/07, James Jacobs <[EMAIL PROTECTED]> wrote:
> Using the start.bat file included with the QEMU package (except changing
> cd-rom and hard disk image filenames as appropriate).
> I haven't adjusted any audio settings, I'm using whatever the defaults
are.
which package ?
you mentionned a
> Using the start.bat file included with the QEMU package (except changing
> cd-rom and hard disk image filenames as appropriate).
> I haven't adjusted any audio settings, I'm using whatever the defaults
are.
which package ?
0.90 has the imagefile bug, so I normally use 0.82 instead
>Not many s
On 3/30/07, James Jacobs <[EMAIL PROTECTED]> wrote:
3 more bugs that need attention...
a) serious: Image files, even those created by the version of qemu-img.exe
that comes with QEMU 0.90, are unreadable by QEMU 0.90, QEMU 0.82 works fine
with them.
b) less serious: "Out of environment space" e
3 more bugs that need attention...
a) serious: Image files, even those created by the version of qemu-img.exe
that comes with QEMU 0.90, are unreadable by QEMU 0.90, QEMU 0.82 works fine
with them.
b) less serious: "Out of environment space" error when starting.
c) serious: "audio: Failed to cre
On Sunday 04 March 2007 11:52, Kirill A. Shutemov wrote:
> I want to help qemu project, but some patches which I post to the mail
> list have ignored. I guess that a open source project should have faster
> feedback.
Giving some description of the patches might help. Patches with no explanation
o
I want to help qemu project, but some patches which I post to the mail
list have ignored. I guess that a open source project should have faster
feedback.
Subject of posts which have still ignored:
[PATCH] syscall mincore
[PATCH] syscall uselib
[BUG] [PATCH] Syscall gethostname fix
[BUG] [PATCH] S
Following is the list of some easy to reproduce bugs in QEMU,
perhaps someone will have motivation to fix them:
Preliminary:
cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/qemu login
cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/qemu co qemu
cd qemu
./configure --target-list=i386-softmmu
make
25 matches
Mail list logo
