Hi All,
man(1) and makemandb(8) take the path of man.conf as an argument using
option -C. To be consistent, apropos(1) and whatis(1) should also
accept the same option, I have made this change.
However, -C option was being used by apropos(1) to disable showing the
context of the match, but using
On May 22, 3:42pm, rhia...@falu.nl (Rhialto) wrote:
-- Subject: Re: PaX MPROTECT gdb and software breakpoints
Here's the sysctl way.
christos
Index: kern/kern_pax.c
===
RCS file: /cvsroot/src/sys/kern/kern_pax.c,v
retrieving revisi
hi,
I'd like to write code that works with the input or output typically
done with ifconfig.
as an example, I would like to know, say, which interfaces are wireless
and which are wired, as they tend to be controlled differently, and
whether they are up.
my options currently seem to be:
1. parse t
On Sun 22 May 2016 at 09:29:17 -0400, Christos Zoulas wrote:
> On May 22, 10:36am, bou...@antioche.eu.org (Manuel Bouyer) wrote:
> -- Subject: Re: PaX MPROTECT gdb and software breakpoints
>
> | I occasionally need to gdb-attach to a running process (usually a daemon)
> | to try to understand what
On May 22, 10:36am, bou...@antioche.eu.org (Manuel Bouyer) wrote:
-- Subject: Re: PaX MPROTECT gdb and software breakpoints
| I occasionally need to gdb-attach to a running process (usually a daemon)
| to try to understand what's going on. I think it's important to keep
| the ability to attach to
Date:Tue, 17 May 2016 16:10:37 +
From:David Holland
Message-ID: <20160517161037.ga1...@netbsd.org>
| On Tue, May 17, 2016 at 04:05:57PM +, Christos Zoulas wrote:
| > In article <17323.1463479...@andromeda.noi.kre.to>,
| > Robert Elz wrote:
| > >Th
uOn Sun, 22 May 2016, Martin Husemann wrote:
On Sat, May 21, 2016 at 04:21:45PM -0400, Christos Zoulas wrote:
There are three solutions I can think of (maybe you can think of a better
one):
1. Leave it as it is and document that people will have to paxctl +m
the executables that they need t
On Sat, May 21, 2016 at 04:21:45PM -0400, Christos Zoulas wrote:
> There are three solutions I can think of (maybe you can think of a better
> one):
>
> 1. Leave it as it is and document that people will have to paxctl +m
>the executables that they need to mprotect before they can debug
>i
On Sat, May 21, 2016 at 04:21:45PM -0400, Christos Zoulas wrote:
>
> Hello,
>
> Now that PaX MPROTECT is the default on 3 platforms (amd64, i386, and evbarm)
> the problem of software breakpoints and gdb has surfaced. Namely if MPROTECT
> is on, and you try to set a breakpoint you get:
>
> (gdb)
