Hi Greg,

the other set of errors was only related to the wrong orientation vector
specified for the BSDF material.
So the only difference that is really there is the one related to mmap().

I also thought about avoiding mmap() on the 32bit machine. For Cygwin this
is done similarly in
common/ezxml.h by defining EZXML_NOMMAP. Maybe that's the best solution for
now.

Thanks for your help!

Cheers,
David



Am 25. April 2012 17:50 schrieb Gregory J. Ward <[email protected]>:

> Hi David,
>
> I have no idea what's going wrong.  You did a test before where you forced
> the program to take the "else" clause to avoid mmap(), and ended up with a
> different set of errors.  Do you not get those errors when you pass the
> same BSDF through the 64-bit version?  This is puzzling to me.
>
> The fact that mmap() is not returning the file contents in 32-bit mode is
> very disturbing.  This sounds like a header issue, but I have no way to
> debug it without downloading and installing ubuntu on a virtual machine.
>  You could try commenting out the madvise() calls, not that I expect it to
> make a difference...
>
> Avoiding the mmap() call should fix the problem, so it's worth trying that
> again.
>
> Cheers,
> -Greg
>
> *From: *David Geisler-Moroder <[email protected]>
>
> *Date: *April 25, 2012 2:19:29 AM PDT
>
> *
> *
>
> Hi Greg,
>
> new/old head versions and different gcc versions do not matter.
>
> The difference is still between 32bit and 64bit.
> Printing out the pointer adress and first char before line 498 in ezxml.c
> *
>         fprintf(stderr, " s = %p\n", s);
>         fprintf(stderr, " s[0] = %c\n", s[0]);
> 498   while (*s && *s != '<') s++; /* find first tag */
> *
> yields:
> (on 32bit):*
>  s = 0xb76fe000
>  s[0] =
> *(on 64bit):*
>  s = 0x7f1179377000
>  s[0] = <
> *
> It seems that the contents of the XML-File are not parsed correctly on the
> 32bit system.
>
> Maybe you have some idea what/where the problem could be?
>
> Best,
> David
>
>
_______________________________________________
Radiance-dev mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-dev

Reply via email to