It looks like the crashes have all been fixed on my end; how's it look for the rest of you guys?
-mental
MenTaLguY wrote:
It looks like the crashes have all been fixed on my end; how's it look for the rest of you guys?
-mental
I don't know of any crashing bugs at the moment. If anyone can tell me how to reproduce one, I would be happy to look at it. I've been getting a bit better recently at finding crashers.
Does anyone have any news on the <text> node rendering on Win32? This one is something I know nothing about, and cannot debug. Maybe using good old fashioned breakpoint tracing?
Bob
Does anyone have any news on the <text> node rendering on Win32? This one is something I know nothing about, and cannot debug. Maybe using good old fashioned breakpoint tracing?
Fred says he won't be able to work on it until the end of the month. So if anyone can look into it, that would be great. His opinion is that we need to switch win32 pango to freetype, which as I understand you have tried already though it crashed.
bulia byak wrote:
Does anyone have any news on the <text> node rendering on Win32? This one is something I know nothing about, and cannot debug. Maybe using good old fashioned breakpoint tracing?
Fred says he won't be able to work on it until the end of the month. So if anyone can look into it, that would be great. His opinion is that we need to switch win32 pango to freetype, which as I understand you have tried already though it crashed.
Heh. I think that it is time for a 3-week holiday!
On Thu, 2004-09-09 at 13:16, bulia byak wrote:
His opinion is that we need to switch win32 pango to freetype,
That won't work; the pango freetype backend depends on fontconfig, and that isn't available on Windows.
(btw, the xft backend is just an extremely thin wrapper around the freetype backend)
-mental
Hi Bob,
On Thu, Sep 09, 2004 at 07:02:11AM -0500, Bob Jamison wrote:
MenTaLguY wrote:
It looks like the crashes have all been fixed on my end; how's it look for the rest of you guys?
-mental
I don't know of any crashing bugs at the moment. If anyone can tell me how to reproduce one, I would be happy to look at it. I've been getting a bit better recently at finding crashers.
Well, there are two bugs open in the debian BTS, the one at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261848 was discussed on this list a while ago, but I don't know if it is fixed. For the other one at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251809 I saw changes in the source, so I built a package from at that time newer sources but got no reply, so I don't know if it is fixed or not. This is also the reason why I did not submit it to the tracker.
Another not crashing related bug is debian #270119, for which I produced a patch, which I will update to cvs if it is tested.
With best regards,
Wolfi
participants (4)
-
Bob Jamison -
bulia byak -
MenTaLguY -
Wolfram Quester