Re: Is it possible to block pending queued RealTime signals (AIO originating)?

2013-01-09 Thread Richard Sharpe
On Tue, 2013-01-08 at 09:20 -0800, Adrian Chadd wrote: > On 8 January 2013 08:15, Richard Sharpe wrote: > > On Tue, 2013-01-08 at 07:36 -0800, Adrian Chadd wrote: > >> .. or you could abstract it out a bit and use freebsd's > >> aio_waitcomplete() or kqueue aio notification. > >> > >> It'll then b

Re: Is it possible to block pending queued RealTime signals (AIO originating)?

2013-01-09 Thread Julian Elischer
On 1/9/13 7:21 AM, Richard Sharpe wrote: On Tue, 2013-01-08 at 09:20 -0800, Adrian Chadd wrote: On 8 January 2013 08:15, Richard Sharpe wrote: On Tue, 2013-01-08 at 07:36 -0800, Adrian Chadd wrote: .. or you could abstract it out a bit and use freebsd's aio_waitcomplete() or kqueue aio notifi

Re: Is it possible to block pending queued RealTime signals (AIO originating)?

2013-01-09 Thread Richard Sharpe
On Wed, 2013-01-09 at 10:06 +0800, David Xu wrote: > [...] > >>> This code won't work, as I said, after the signal handler returned, > >>> kernel will copy the signal mask contained in ucontext into kernel > >>> space, and use it in feature signal delivering. > >>> > >>> The code should be modified

Re: malloc+utrace, tracking memory leaks in a running program.

2013-01-09 Thread Alfred Perlstein
On 12/23/12 12:28 PM, Jason Evans wrote: On Dec 21, 2012, at 7:37 PM, Alfred Perlstein wrote: So the other day in an effort to debug a memory leak I decided to take a look at malloc+utrace(2) and decided to make a tool to debug where leaks are coming from. A few hours later I have: 1) a new

Re: malloc+utrace, tracking memory leaks in a running program.

2013-01-09 Thread Alfred Perlstein
On 1/10/13 1:41 AM, Alfred Perlstein wrote: On 12/23/12 12:28 PM, Jason Evans wrote: On Dec 21, 2012, at 7:37 PM, Alfred Perlstein wrote: So the other day in an effort to debug a memory leak I decided to take a look at malloc+utrace(2) and decided to make a tool to debug where leaks are comin

Re: malloc+utrace, tracking memory leaks in a running program.

2013-01-09 Thread Konstantin Belousov
On Thu, Jan 10, 2013 at 01:56:48AM -0500, Alfred Perlstein wrote: > Here are more convenient links that give diffs against FreeBSD and > jemalloc for the proposed changes: > > FreeBSD: > https://github.com/alfredperlstein/freebsd/compare/13e7228d5b83c8fcfc63a0803a374212018f6b68~1...utrace2 > Why