[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Apparent malloc from signal handler

From: Brian Bloniarz
Subject: Apparent malloc from signal handler
Date: Mon, 30 Jul 2012 12:10:42 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0

Hi, I think I've stumbled on bug involving memory allocation from signal 
context in
ncurses 5.9. In GDB, I see this traceback:

#1  0x00007f2289120cb1 in _L_lock_10627 () at malloc.c:5209
#2  0x00007f228911ea37 in __GI___libc_malloc (bytes=139786308626208) at 
#3  0x00007f2287b180cb in _nc_set_buffer () from 
#4  0x00007f2287b16e6d in reset_prog_mode () from 
#5  0x00007f2287d4b1d5 in doupdate () from 
#6  0x00007f2287d41ee5 in ?? () from /lib/x86_64-linux-gnu/libncursesw.so.5
#7  <signal handler called>

I think the callchain that's involved is:

More details: I'm running ncurses version 5.9-4 from Ubuntu 12.04. The symptom 
is a
deadlock in ipython -- it looks like ipython uses readline and ncurses, and I 
think both
are incorrectly doing memory allocation from signal context. I don't have any 
reliable way
to reproduce the issue but I've seen it several times.

Please let me know if I can help at all diagnosing or fixing this.

Thanks & kind regards,
Brian Bloniarz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]