On Mon, Aug 06, 2007 at 12:23:56PM -0600, Orion Poplawski wrote:
> The python examples x01 and x09 hang in an infinite loop on Fedora 7 on
> ppc64. The loop is in plline.c in grdashline :
>
>
> (gdb) print plsc->pendn
> $1 = 1
> (gdb) print plsc->space
> $2 = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0}
> (gdb) print plsc->curel
> $3 = 0
> (gdb) print plsc->nms
> $4 = 1
> (gdb) print plsc->mark
> $5 = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0}
>
OK. I think I know what the problem is. Both the mark and the space
arrays are blank, and so the dashed line is undefined. The problem must
be with plstyl and not with plline. plstyl takes two arrays of PLINT as
arguments.
I have recently altered this code since it was not 64-bit clean and did
not work on 64-bit sytems. I managed to get it working on a 64-bit intel
based system, but it clearly doesn't work on a 64-bit PPC. From this I
conjecture that it is an endian issue. PPC linux is big-endian isn't it?
The code you need to check is in bindings/python/plplotcmodule.i.
svn diff -r 7764:7765 bindings/python/plplotcmodule.i
will show you the relevant changes.
Things to check:
What size are int and long on your architecture?
Do you have stdint.h? (Should be a yes)
What is the python SIZEOF_LONG defined as - this is the default python
integer size. Plplot works with a 32-bit int.
myIntArray_ContiguousFromObject is the function doing the casting. This
is based on the floating point equivalent. Does single precision
floating point work on your architecture?
Andrew
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
