Samuel Thibault, on Wed 16 Nov 2016 19:50:07 +0100, wrote:
> Samuel Thibault, on Wed 16 Nov 2016 19:46:52 +0100, wrote:
> > The attached testcase does get the faulting address.
>
> And the attached testcase doesn't.
And is fixed by the attached patch, could you try it?
Samuel
Index: glibc-2.24/s
Samuel Thibault, on Wed 16 Nov 2016 19:46:52 +0100, wrote:
> The attached testcase does get the faulting address.
And the attached testcase doesn't.
> I really believe the issue is related to this:
Confirmed :)
> > Note that there is a
> >
> > /* XXX what if handler != action->handler (for
Samuel Thibault, on Mon 14 Nov 2016 01:07:40 +0100, wrote:
> > Once that's been resolved, then we're back to the problem with signal
> > preemptors! libpager/pager-memcpy.c includes the following code:
> >
> > void fault (int signo, long int sigcode, struct sigcontext *scp)
> > {
> >
On Wed, Nov 16, 2016 at 11:03:44AM +0100, Riccardo Mottola wrote:
> Miguel Figueiredo wrote:
> >I think not. I've "always" seen one the annoying small thing in aptitude
> >in Hurd, pressing q to quit and it does not quits. If i repeat the q and
> >then Ctrl+C, it quits and I see the on the con
Hi,
Richard Braun wrote:
I increased the allocated RAM size of the VM to 1024MB and now I read this:
Try 2g or even 3g.
I can't allocate more.. 2G is about the limit for my host, but I did
allocate 2048 MB of ram, did a "fresh boot", accessed directly root and
started aptitude and issued "
Hi,
Miguel Figueiredo wrote:
I think not. I've "always" seen one the annoying small thing in
aptitude in Hurd, pressing q to quit and it does not quits. If i
repeat the q and then Ctrl+C, it quits and I see the on the console.
I've seen this on Virtualbox, but now i have it on qemu with th
