On Oct 25, 2008, at 4:56 PM, Hezekiah M. Carty wrote:
> While testing trying to patch the recently discussed multiple output
> streams with the same driver bug I found something that is possibly
> useful for diagnosing this Cairo segmentation fault issue, and
> certainly useful as a workaround oth
On Wed, Mar 19, 2008 at 9:51 PM, Hazen Babcock <[EMAIL PROTECTED]> wrote:
> Agreed, but the segfault occurs because I did not think to check the
> return value of the function pango_cairo_create_layout(). It should
> return a pointer to a PangoLayout, but when it fails, as it does in
> our test cas
On Wed, Mar 19, 2008 at 9:51 PM, Hazen Babcock <[EMAIL PROTECTED]> wrote:
> Agreed, but the segfault occurs because I did not think to check the
> return value of the function pango_cairo_create_layout(). It should
> return a pointer to a PangoLayout, but when it fails, as it does in
> our test cas
On May 19, 2008, at 6:12 PM, Hezekiah M. Carty wrote:
> On Wed, Mar 19, 2008 at 9:51 PM, Hazen Babcock <[EMAIL PROTECTED]>
> wrote:
>>
>> Agreed, but the segfault occurs because I did not think to check the
>> return value of the function pango_cairo_create_layout(). It should
>> return a point
On Wed, Mar 19, 2008 at 9:51 PM, Hazen Babcock <[EMAIL PROTECTED]> wrote:
>
> Agreed, but the segfault occurs because I did not think to check the
> return value of the function pango_cairo_create_layout(). It should
> return a pointer to a PangoLayout, but when it fails, as it does in
> our test c
On Mar 13, 2008, at 2:42 AM, Alan W. Irwin wrote:
> The other point I want to make concerns segfaults which are defined as
> follows (by wikipedia): "A segmentation fault occurs when a program
> attempts
> to access a memory location that it is not allowed to access, or
> attempts to
> access
On Thu, Mar 13, 2008 at 12:53 AM, Jonathan Woithe
<[EMAIL PROTECTED]> wrote:
> > On Wed, Mar 12, 2008 at 11:12 PM, Jonathan Woithe
> > <[EMAIL PROTECTED]> wrote:
> > > I agree. What about running ldd on /lib/plplot-*/cairo.so?
> > > Anything differences in this between the two working directo
> > I suspect there might be some issue going on between the different versions
> > of plplot on your system. It would be nice to pinpoint the exact cause.
>
> Hazen and Hez may be comparing apples and oranges.
I agree. The circumstances on the systems are different and I suspect that
the root
On 2008-03-13 15:23+1030 Jonathan Woithe wrote:
> I suspect there might be some issue going on between the different versions
> of plplot on your system. It would be nice to pinpoint the exact cause.
Hazen and Hez may be comparing apples and oranges.
One result is the build-tree result. By des
> On Wed, Mar 12, 2008 at 11:12 PM, Jonathan Woithe
> <[EMAIL PROTECTED]> wrote:
> > I agree. What about running ldd on /lib/plplot-*/cairo.so?
> > Anything differences in this between the two working directories?
> >
> > The drivers are loaded dynamically on demand I think which is why the cai
On Wed, Mar 12, 2008 at 11:12 PM, Jonathan Woithe
<[EMAIL PROTECTED]> wrote:
> I agree. What about running ldd on /lib/plplot-*/cairo.so?
> Anything differences in this between the two working directories?
>
> The drivers are loaded dynamically on demand I think which is why the cairo
> librar
> >> Curiously I found that if I ran my test program in the directory that
> >> I had make install plplot from then I didn't see the problem. I have
> >> the following the layout:
> >> /home/hbabcock/C/plplot_test/test1 - the test program.
> >> /home/hbabcock/OpenSource/plplot-working/plplot-CBS-1
I forgot to CC: the list...
On Wed, Mar 12, 2008 at 10:17 PM, Hazen Babcock <[EMAIL PROTECTED]> wrote:
> ldd looks normal (at least to me):
> debian ~/C/plplot_test : ldd test1
> linux-gate.so.1 => (0xe000)
> libplplotd.so.9 => /usr/local/lib/libplplotd.so.9 (0xb7eb2000)
>
On Mar 11, 2008, at 10:51 PM, Jonathan Woithe wrote:
>> The problem seems to start in the proc_str() function at:
>> layout = pango_cairo_create_layout(aStream->cairoContext);
>> though it makes through several more lines of code before going down
>> for good.
>>
>> Curiously I found that if I ra
> The problem seems to start in the proc_str() function at:
> layout = pango_cairo_create_layout(aStream->cairoContext);
> though it makes through several more lines of code before going down
> for good.
>
> Curiously I found that if I ran my test program in the directory that
> I had make ins
On Mar 11, 2008, at 10:17 PM, Hazen Babcock wrote:
>
> I'm not seeing this on OS-X, but I am seeing it on my linux box so
> perhaps something changed between versions of the cairo library?
>
> PPC/64, pango 1.15.5, cairo 1.2.6. Ok.
>
> Intel/32, pango 1.16.5, cairo 1.4.10. Not Ok.
The problem see
On Mar 11, 2008, at 2:10 AM, Alan W. Irwin wrote:
> On 2008-03-11 00:01-0400 Hezekiah M. Carty wrote:
> Thanks for spotting this issue which I have just confirmed with the
> pscairo
> device using a freshly compiled svn version of PLplot on Debian
> testing. I
> used the following test C cod
On 2008-03-10 23:10-0700 Alan W. Irwin wrote:
> If the cairo device drivers does not properly shut down libcairo at plend
> you could get memory management problems with symptoms like what we are
> seeing. I suggest you look carefully at what the working psttf.c device
> driver does in this regar
On 2008-03-11 00:01-0400 Hezekiah M. Carty wrote:
> I think I have found a consistent segmentation fault while using the
> xcairo and pngcairo plotting devices under PLplot 5.9.0 (Debian
> packages) and svn head on Debian Sid, x86-32. I have not tested the
> other *cairo devices, but given the er
On Tue, Mar 11, 2008 at 12:01 AM, Hezekiah M. Carty
<[EMAIL PROTECTED]> wrote:
> I think I have found a consistent segmentation fault while using the
> xcairo and pngcairo plotting devices under PLplot 5.9.0 (Debian
> packages) and svn head on Debian Sid, x86-32. I have not tested the
> other *
I think I have found a consistent segmentation fault while using the
xcairo and pngcairo plotting devices under PLplot 5.9.0 (Debian
packages) and svn head on Debian Sid, x86-32. I have not tested the
other *cairo devices, but given the error messages I think it would
affect others as well.
The f
21 matches
Mail list logo
