octave-maintainers
[Top][All Lists]
Advanced

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

Re: 3.6.0 release


From: Michael D Godfrey
Subject: Re: 3.6.0 release
Date: Tue, 29 Nov 2011 11:56:49 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

On 11/29/2011 10:45 AM, John W. Eaton wrote:
Yes.  I even did the bisecting twice because I couldn't believe that
this could be the changset that caused it.  Then I tried the above
change on the current sources with the same effect.

| This must the symptom of something else (like uninitialized memory).
| Forcing the use of the octave allocator is IMO not a solution.

Absolutely, this can't be the fix.  But when I run with valgrind with
and without the above change, nothing obvious about uninitialized
memory pops up.  However, there are some messages related to
fontconfig (I think) in both cases.  I'll check again and try to send
details later.
Just to add one more test:  this "fix" works on fedora 14, and I am sure,
on other Fedora releases.  It is obviously important to discover why this
has the effect that it does.  The real problem likely has (not good) effects
elsewhere.  Sadly, I do not really know where to start to help with this.
Very mysterious.

The fontconfig item may be relevant.  I notice when I run the legend test
without the "fix"  the plot window "flickers" which could suggest that
the legend is being drawn, but without the text which got lost due to
a font error.  Pure speculation on my part.

Michael


reply via email to

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