Hi!
On 20:47 Thu 13 Oct , Richard Weinberger wrote:
> Am 13.10.2011 20:10, schrieb mic...@michaelblizek.twilightparadox.com:
> > After migrating from i386 to x86_64, my uml started to segfault in weird
> > ways.
>
> What exactly is the problem?
> Without any details nobody can and will help you.
Hi!
After migrating from i386 to x86_64, my uml started to segfault in weird ways.
In the end, I figured that "make clean/mrproper/distclean" does not really
clean up properly. I had to use "ARCH=um make distclean". The command "make
distclean" did not remove these files:
arch/um/include/shared/k
Am 13.10.2011 20:10, schrieb mic...@michaelblizek.twilightparadox.com:
> After migrating from i386 to x86_64, my uml started to segfault in weird ways.
What exactly is the problem?
Without any details nobody can and will help you.
> In the end, I figured that "make clean/mrproper/distclean" does
Hi Jeff, all,
On Thu, Oct 13, 2011 at 3:35 AM, Jeff Dike wrote:
> UML uses separate address spaces for its processes, thus
> they don't look like threads to anything else, but the bulk of the
> memory (the UML kernel) in those address spaces is shared.
Is it technically feasible to modify UML so
