Re: PaX MPROTECT gdb and software breakpoints

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

Re: PaX MPROTECT gdb and software breakpoints

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 tr

Re: PaX MPROTECT gdb and software breakpoints

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

Re: PaX MPROTECT gdb and software breakpoints

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

Re: PaX MPROTECT gdb and software breakpoints

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: > >

Re: PaX MPROTECT gdb and software breakpoints

On 21 May 2016 at 21:21, 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: > >