Alan W. Irwin wrote:
> On 2009-02-11 14:01-0700 Orion Poplawski wrote:
>
>> Fedora is moving to gcc 4.4 with Fedora 11. I'm trying to build plplot
>> 5.9.2 and getting the following error:
>
>> fci = 0xbf947ae1
>
> Hi Orion:
>
> Just in case you didn't know this already, what distinguishes an FCI from
> UCS4 code is the most significant bit is turned on (see
> http://plplot.sourceforge.net/docbook-manual/plplot-html-5.9.2/characters.html#fci).
> So the above hex pattern does qualify as an FCI, and that is why you got
> into the FCI part of the code.
> However, other than that marker bit, the other thing that distinguishes FCI's
> is only their 3 lowest order hex fields are set. So valid values look like
> 0x80000???. Clearly, the above value is completely invalid if interpreted
> as an FCI rather than an ordinary UCS4 character. However, the maximum
> UCS4 is supposed to be 0x10FFFF so the above is not consistent with UCS4
> either. Thus, I think the basic problem is
> that garbage is getting into the array we use to hold a combination of UCS4
> and FCI 32-bit unsigned integers.
>
>> Seems like I need to track down where fci is getting set incorrectly?
>
> Yes or investigate where an ordinary UCS4 code is being set to garbage.
>
breaking on c_plsfci, I get to:
Breakpoint 3, c_plsfci (fci=1066695393) at
/builddir/build/BUILD/plplot-5.9.2/src/plcore.c:3018
3018 plsc->fci = fci | PL_FCI_MARK;
which again seems like a bad fci number.
(gdb) print /x fci
$2 = 0x3f947ae1
(gdb) bt
#0 c_plsfci (fci=1066695393) at
/builddir/build/BUILD/plplot-5.9.2/src/plcore.c:3018
#1 0x0000040000065184 in plsfci_ (fci=<value optimized out>)
at /builddir/build/BUILD/plplot-5.9.2/bindings/f77/scstubs.c:781
#2 0x0000000010001e84 in x23f ()
at /builddir/build/BUILD/plplot-5.9.2/fedora/examples/f77/x23f.f:326
#3 0x0000000010004078 in .main ()
#4 0x00000400005412b8 in .generic_start_main () from /lib64/libc.so.6
#5 0x00000400005414d0 in .__libc_start_main () from /lib64/libc.so.6
#6 0x0000000000000000 in ?? ()
(gdb) up
#1 0x0000040000065184 in plsfci_ (fci=<value optimized out>)
at /builddir/build/BUILD/plplot-5.9.2/bindings/f77/scstubs.c:781
781 c_plsfci(f);
(gdb) list
776 void
777 PLSFCI(PLINT64 *fci)
778 {
779 PLUNICODE f;
780 f = (PLUNICODE) (*fci & 0xffffffff);
781 c_plsfci(f);
782 }
783
784 void
785 PLSFNAM7(const char *fnam)
(gdb) print f
No symbol "f" in current context.
(gdb) print fci
$3 = <value optimized out>
(gdb) up
#2 0x0000000010001e84 in x23f ()
at /builddir/build/BUILD/plplot-5.9.2/fedora/examples/f77/x23f.f:326
326 call plsfci(0)
So looks like we are definitely having some variable type issues going
from Fortran to C.
> Have you had success before with your ppc hardware?
Compiles fine on ppc with gcc 4.3, new issue with 4.4. Now whether it
is really a bug in gcc or simply stricter language adherence is yet to
be determined.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane or...@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
