There is indeed a bug in the release in that area; xpdf is known to
crash with it.
I thought I had the problem figured out but then this turned up.
I have a version that leaks like hell but that xpdf works with,
and as you note the latest release is the other way around.
More digging ...
Danny
On Tue, 2004-11-23 at 15:47, Allin Cottrell wrote:
> I'm not sure if the bug lies with xpdf or lesstif, but current xpdf
> (3.00) crashes on startup when linked against lesstif 0.93.97, while
> it runs OK when linked to lesstif 0.93.94.
>
> I have not myself compiled the programs with debugging, but someone
> else has a backtrace at
>
> http://www.mail-archive.com/[email protected]/msg01742.html
>
> which indicates that the segfault occurs in XmFontListCopy, in
> lesstif's Label.c. I notice that there has been a fair amount of
> CVS activity in relation to this file, with various people talking
> about fixing memory leaks (but not sounding super-confident
> about the fixes!).
>
> Please consider the possibility that a leak "fix" has broken
> something in Label.c. Thanks.
--
Danny Backx - danny.backx-at-scarlet.be http://up.to/danny.backx
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Lesstif-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/lesstif-discuss
