Follow-up Comment #3, bug #17874 (project mc):
I absolutelly don't know why mc passes here NULL.
Are there ways to make mc behave better in this respect? If not please close
invalid.
___
Reply to this item at:
Follow-up Comment #4, bug #17874 (project mc):
The only way I know is to fix liblow.c. After my fix, I have never seen a
crash again.
May be that it could be somehow caused by mc - creating terminal, but I don't
know internals.
___
Reply
Update of bug #17874 (project mc):
Status:None = Invalid
Open/Closed:Open = Closed
___
Reply to this item at:
Follow-up Comment #2, bug #17874 (project mc):
The crash that you see has nothing to do with MC. The backtraces do not
provide any evidence to support your theory. It must be an gpm issue.
___
Reply to this item at:
URL:
http://savannah.gnu.org/bugs/?17874
Summary: Crashing inside liblow.c
Project: GNU Midnight Commander
Submitted by: fojtik
Submitted on: Wednesday 09/27/2006 at 19:43
Category: None
Severity: 3 -
Follow-up Comment #1, bug #17874 (project mc):
Acconding to further analysis, I have found a fix inside liblow.c
I absolutelly don't know why mc passes here NULL. May be that new glibc is
more sensitive to NULL than old one. (mc -d is also workaround, but this
don't kill mouse.)
/* do we really
