Take a look at: http://lists.cs.uiuc.edu/pipermail/lldb-dev/2013-July/002009.html
It's not a pretty work around, but you can handle the exception by taking over EXC_BAD_ACCESS on the thread port before lldb gets to it on the thread exception port. Have you filed a radar? > On Oct 30, 2014, at 00:35, Brian Demsky <[email protected]> wrote: > > Hi Jeremy, > > My use case is the following. I have a snapshotting routine that uses page > protection combined with a signal handler for SIGBUS and SIGSEGV. > > If you try to debug code that uses it under lldb, it catches the mach kernel > signal EXC_BAD_ACCESS and stops the program instead of passing the signal to > the handle. The process handle commands don’t to support overriding that > behavior. > > gdb has the “set dont-handle-bad-access 1” option to avoid stopping on bad > accesses. > > Brian > >> On Oct 29, 2014, at 11:31 PM, MacPorts <[email protected]> wrote: >> >> #42796: gdb-apple @1824: build failure due to texinfo5 >> ------------------------+------------------------ >> Reporter: egall@… | Owner: jeremyhu@… >> Type: defect | Status: closed >> Priority: Normal | Milestone: >> Component: ports | Version: 2.2.1 >> Resolution: fixed | Keywords: >> Port: gdb-apple | >> ------------------------+------------------------ >> Changes (by jeremyhu@…): >> >> * status: new => closed >> * resolution: => fixed >> >> >> Comment: >> >> Submitted in r127586, but I still want to know what your use case is. >> >> -- >> Ticket URL: <https://trac.macports.org/ticket/42796#comment:10> >> MacPorts <https://www.macports.org/> >> Ports system for OS X >> > _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
