On Wed, Aug 11, 2010 at 1:52 AM, syd adams <adams....@gmail.com> wrote:
> Well I tried again , no luck , still getting the same error , and also with
> and older fgfs build .... makes me suspect something wrong in fgdata .
> I'll report if I discover the problem before it fixes itself :)
simgear/scene/material/Effect.cxx line 878 should be:
{"bool", Uniform::BOOL},
That is a member of the collection that findAttr eventually searches.
If the entry is there you shouldn't get the error. That must mean you
still have your FG compiled with old simgear. Of course this also
happens with old FG, since that is definitely missing this. It is not
"something wrong with data" it is simply "FG too old to handle new
data".
A somewhat tedious way to verify your fgfs binary:
$ objdump -C -t fgfs | grep uniformTypesInit
0000000000df3b80 g O .data 00000000000000b0
simgear::uniformTypesInit
$ objdump --start-address=0xdf3b80 --stop-address=$((0xdf3b80+7)) -j
.data -s fgfs
fgfs: file format elf64-x86-64
Contents of section .data:
df3b80 752aa700 000000 u*.....
$ objdump --start-address=0xa72a75 --stop-address=$((0xa72a75+5)) -j
.rodata -s fgfs
fgfs: file format elf64-x86-64
Contents of section .rodata:
a72a75 626f6f 6c00 bool.
(For this last command, you have to account for little-endian
addresses. The bytes in the dump were 752aa700, they have to be
reversed to get the address that's how the 0xa72a75 came to be.)
--
Csaba/Jester
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
