This is normal, the file is supposed to be generated by running the
game_skel-1.py tuto.
Ok, I added a print statement explaining this fact.
___
Soya-user mailing list
Soya-user@gna.org
https://mail.gna.org/listinfo/soya-user
Jiba wrote:
Ok, I've added this compile flag (I prefer this solution to Greg's one,
> because one may write new code and ignore that all char would need to be
> explicitely marked as signed or unsigned).
Certainly it's an easier way of fixing it in the short term,
but I still think it would be
On Sat, 02 Sep 2006 12:46:07 +0200
souvarine <[EMAIL PROTECTED]> wrote:
> I finaly found out what that "bug" realy is. Everything is explained here
> http://www.technovelty.org/code/c/ppc-char.html
>
> So actualy there were no bug in Soya. The problem is that the type char
> is signed by default
souvarine wrote:
I suggest to add -fsigned-char to soya's
compilation flags to prevent this kind of problem to happend again.
A better way would be not to write code that depends
on the signedness of chars, since it's non-portable.
--
Greg
___
Soya-
I finaly found out what that "bug" realy is. Everything is explained here
http://www.technovelty.org/code/c/ppc-char.html
So actualy there were no bug in Soya. The problem is that the type char
is signed by default on pc and unsigned by default on mac (even with
linux). Because of this little nuan
Bug fixed ! I had a hard time finding it. The problem was the cast in
terrain.pyx line 859. For unknown reason it don't work properly on my mac.
The bug happend when self._max_level + 1 - (d / r) = -1 the result
of the cast from int to char is 255. I don't understant why, I never
experienced this
C doesn't "know" when a stack overflow occurs. So it would try to read/write out of the stack segment, resulting in a segfault.On 8/30/06, Jiba
<[EMAIL PROTECTED]> wrote:> (gdb) bt
> #0 0x0fbadd24 in __pyx_f_5_soya_8_Terrain__tri_split> (__pyx_v_self=0x1066e1d0, __pyx_v_tri=0x106e93b0) at _soya.c
> (gdb) bt
> #0 0x0fbadd24 in __pyx_f_5_soya_8_Terrain__tri_split
> (__pyx_v_self=0x1066e1d0, __pyx_v_tri=0x106e93b0) at _soya.c:55320
> #1 0x0fbadd88 in __pyx_f_5_soya_8_Terrain__tri_split
> (__pyx_v_self=0x1066e1d0, __pyx_v_tri=0x106e94b8) at _soya.c:55328
> #2 0x0fbadd88 in __pyx_f_5_soya_8_T
This is normal, the file is supposed to be generated by running the
game_skel-1.py tuto.
Ok, I added a print statement explaining this fact.
___
Soya-user mailing list
Soya-user@gna.org
https://mail.gna.org/listinfo/soya-user
On Sun, 27 Aug 2006 23:37:39 +0200
marmoute <[EMAIL PROTECTED]> wrote:
>
> On 27 août 06, at 22:37, souvarine wrote:
>
> > The more I make experiment with Soya the more I have segfault
> > problems,
> > and not only when I modify camera.back :(
> > It only append on my Mac, not on my PC (both
Use GDB with python is easier than I thought.
I tested two segfaulting code. First the game_skel-1.py, that one always
end by a segfault. It did since the first time I tried Soya on my mac
but back then I just didn't paid attention to it.
(gdb) run game_skel-1.py
Starting program: /usr/bin/python
On Sun, 27 Aug 2006 22:37:16 +0200
souvarine <[EMAIL PROTECTED]> wrote:
> The more I make experiment with Soya the more I have segfault problems,
> and not only when I modify camera.back :(
> It only append on my Mac, not on my PC (both on Linux) so now I think
> there must be something like an e
On 27 août 06, at 22:37, souvarine wrote:
The more I make experiment with Soya the more I have segfault
problems,
and not only when I modify camera.back :(
It only append on my Mac, not on my PC (both on Linux) so now I think
there must be something like an endian problem somewhere in the
The more I make experiment with Soya the more I have segfault problems,
and not only when I modify camera.back :(
It only append on my Mac, not on my PC (both on Linux) so now I think
there must be something like an endian problem somewhere in the core of
Soya.
I would like to track it down. Do yo
On Thu, 17 Aug 2006 20:13:16 +0200
souvarine <[EMAIL PROTECTED]> wrote:
> Hi all.
>
> I have the SVN version of Soya installed. I'm playing with the
> game_skel-5.py tutorial. When I set camera.back to a value superior to
> 80.0 the program exit with a segmentation fault shortly after I start
> i
Hi all.
I have the SVN version of Soya installed. I'm playing with the
game_skel-5.py tutorial. When I set camera.back to a value superior to
80.0 the program exit with a segmentation fault shortly after I start
it. Is this a bug ?
Souvarine.
___
Soya-
16 matches
Mail list logo
