I would think keeping it simple with accessor functions on SBProcess would be the way to go. We should be able to read the current settings for each signal, and set them. Maybe something like:
bool SBProcess::GetUnixSignalSettings (int signo, bool ¬ify, bool &stop, bool &suppress); bool SBProcess::SetUnixSignalSettings (int signo, bool notify, bool stop, bool suppress); On Jun 18, 2013, at 1:57 AM, Russell Harmon <[email protected]> wrote: > I'm currently thinking wrapping the UnixSignals object into an SBUnixSignals, > or would you prefer an API in SBProcess which is restricted to only > ShouldNotify, ShouldStop and ShouldSuppress? > > -- > Russell Harmon > > > On Mon, Jun 17, 2013 at 11:27 AM, Greg Clayton <[email protected]> wrote: > Doesn't look like it. Feel free to propose a new API for SBProcess. > > On Jun 16, 2013, at 5:27 AM, Russell Harmon <[email protected]> wrote: > > > Is there currently a way to configure LLDB's signal disposition via it's > > API? I'm not seeing a way. > > -- > > Russell Harmon > > _______________________________________________ > > lldb-dev mailing list > > [email protected] > > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
