13 May
2009
13 May
'09
7:11 a.m.
Bob Jamison wrote:
I must say, the title "Don't let Inkscape Crash" is probably the best title for a bug ever filed for IS.
It is maybe dating me, but in the past, if a malloc() causes problems, it is because somebody has done something bad with a previously- allocated malloc() chunk.
Indeed, it seems odd to "fix" Inkscape by letting g_(try_)new fail silently, possibly creating problems at a later date or masking previous problems... Or did most of the code using g_new simply assume that it would return a null pointer (handling it appropriately)?