Dear Maintainer,
I tried to find some more information about this issue.
Attached is a file containing some hints how I did run
the UML process and some debugging output.
As far as I see it is yet another issue with some "caddr32_t"
sizes, this time they are used to map the input data.
Therefore
For me, slirp:amd64 does not crash, but does not work either (with User
Mode Linux). Installing slirp:i386 on an amd64 system works.
Cheers,
--
Stéphane
On Wed, 2020-01-15 at 22:49 +0100, Roberto Lumbreras wrote:
> Hi,
>
> Could you please send me how to reproduce the bug?
> It just works for me... but for sure my setup is different.
I'm trying to use UML with slirp and it crashes before i even manage to
setup a network connection :/
I can have
Hi,
Could you please send me how to reproduce the bug?
It just works for me... but for sure my setup is different.
On Wed, Jan 15, 2020 at 10:03 PM Sjoerd Simons wrote:
> Package: slirp
> Version: 1:1.0.17-9
> Severity: important
>
> The last upload fixes slirp crashes directly on startup on
Package: slirp
Version: 1:1.0.17-9
Severity: important
The last upload fixes slirp crashes directly on startup on amd64; It now just
crashes
when starting to use it
backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x5567818fa30b in tcp_reass
5 matches
Mail list logo
