Follow-up Comment #2, bug #29050 (project screen):
Thanks. The valgrind log is very useful. One of the invalid memory reads was
fixed earlier (in 4f28ba8c8f). I have committed a fix for the remaining
invalid reads (da8e87d6505). If you run screen in valgrind again, if you could
use the latest version, that would be great. Thanks again!
To get a coredump, do you have 'ulimit -c' set appropriately? (I set 'ulimit
-c unlimited' myself).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?29050>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
