On 27/11/2017 14:10, John Paul Adrian Glaubitz wrote:
> On 11/27/2017 05:07 PM, Adhemerval Zanella wrote:> However I am not very
> compelled to change internal posix_spawn
>> on GLIBC on Linux mainly because it uses a slight less resources
>> than the generic POSIX one (check e83be730910c) and
On 11/27/2017 05:07 PM, Adhemerval Zanella wrote:> However I am not very
compelled to change internal posix_spawn
on GLIBC on Linux mainly because it uses a slight less resources
than the generic POSIX one (check e83be730910c) and it works
on Linux kernel as expected.
But it breaks QEMU and
On 27/11/2017 13:24, Peter Maydell wrote:
> On 27 November 2017 at 12:57, Adhemerval Zanella
> wrote:
>> We found out this potential bogus assert on 2.27 development [1] which
>> resulted in two fixes [2][3].
>>
>> It should not be an issue for generic posix_spawn
On 27 November 2017 at 12:57, Adhemerval Zanella
wrote:
> We found out this potential bogus assert on 2.27 development [1] which
> resulted in two fixes [2][3].
>
> It should not be an issue for generic posix_spawn usage where there is
> no expectation
On 26/11/2017 18:35, John Paul Adrian Glaubitz wrote:
> On 11/26/2017 09:28 PM, John Paul Adrian Glaubitz wrote:
>> I'm not sure yet what the actual problem is but I thought it should be
>> necessary
>> to point you at the problem.
>
> Ok, there is already a QEMU bug report for this [1].
>
>
On 11/26/2017 09:28 PM, John Paul Adrian Glaubitz wrote:
> I'm not sure yet what the actual problem is but I thought it should be
> necessary
> to point you at the problem.
Ok, there is already a QEMU bug report for this [1].
Adrian
> [1] https://bugs.launchpad.net/qemu/+bug/1673976
--
Hi Rasmus!
Your recent commit "linux: spawni.c: simplify error reporting to parent"
apparently
broke both qemu-user and Microsoft's Windows Services for Linux which both fail
with:
dpkg: warning: ignoring pre-dependency problem!
Preparing to unpack .../archives/bash_4.4-5_m68k.deb ...
preinst: