Hello,
I received the following bug report for the debian package of
foobillard. I can reproduce the segfault on joining a game here.
gdb tells me:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 17430)]
0x10023304 in proceed_dt (balls=0x100b1594, borders=0x100b15ac,
dt=0.00749999983) at billmove.c:1352
1352 dr=vec_diff(balls->ball[i].r,borders->hole[j-1].pos);
(gdb) print j
$4 = -338076354
(gdb) print balls->ball[0]
$8 = {m = 9.11040184e-41, I = 5.69453076e+32, d = 3.53397748e-38, r = {x =
4.36045376e+27, y = 2.92625198e+29, z = 8.2489101e+24}, v = {x =
9.59301603e-39,
y = 2.74541404e+20, z = 1.09032632e+27}, w = {x = 3.17299506e+30, y =
7.69397838e+35, z = -1.36263819e-33}, b = {{x = nan(0x400000), y =
nan(0x400000),
z = nan(0x400000)}, {x = nan(0x400000), y = nan(0x400000), z =
nan(0x400000)}, {x = nan(0x400000), y = nan(0x400000), z = nan(0x400000)}}, nr
= 0,
in_game = 986455359, in_fov = 0, in_hole = -338076354, path = 0xe4a61cbf,
pathsize = -1625255106, pathcnt = -2120008641}
Since j comes from in_hole, it looks to me as if the balls->ball[] structures
are not properly initialized.
Frank
----- Forwarded message from Michael Ablassmeier <[EMAIL PROTECTED]> -----
hi,
Foobillard's Networking modus is pretty annoying to play, it often bails
out with the following error message during the game:
shoot: handling unresolved net request
or segfaults, if you try to join a game:
Fatal signal: Segmentation Fault (SDL Parachute Deployed)
leaving the foobillard which hosts the session eating 100% CPU.
bye,
- michael
----- End forwarded message -----
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
