gdb handling of Mach exceptions

Hi - I've been trying to use gdb on ext2fs when it runs out of disk space and starts generating memory access exceptions. It doesn't behave right. The memory faults get reported as unknown signals and the program can't be restarted: Program received signal ?, Unknown signal. [Switching to

Re: rpctrace / libpager / signal preemptor

On Sun, 2016-11-20 at 21:50 -1000, Brent W. Baccala wrote: > On Sun, Nov 20, 2016 at 5:37 AM, Samuel Thibault > wrote: > > Samuel Thibault, on Sun 20 Nov 2016 14:50:50 +0100, wrote: > >  > Sorry I haven't answered for a few days.  I've been trying to test your patch > by

Re: gdb handling of Mach exceptions

Hello, Brent W. Baccala, on Sun 20 Nov 2016 22:03:51 -1000, wrote: > Obviously, tacking a Mach-specific include into signals.c isn't the right > solution, so can somebody suggest a proper fix? Better ask a gdb list :) Samuel

Re: rpctrace / libpager / signal preemptor

Hello, Brent W. Baccala, on Sun 20 Nov 2016 21:50:04 -1000, wrote: > I suppose I could test your patch just by building the > library itself, but the Debian package build calls "make check" and it's > causing me all kinds of grief. You can use export DEB_BUILD_OPTIONS=nocheck to avoid that,

Re: rpctrace / libpager / signal preemptor

Samuel Thibault, on Mon 21 Nov 2016 09:16:19 +0100, wrote: > Brent W. Baccala, on Sun 20 Nov 2016 21:50:04 -1000, wrote: > > I suppose I could test your patch just by building the > > library itself, but the Debian package build calls "make check" and it's > > causing me all kinds of grief. > >