Jump to content
Eternal Lands Official Forums
Sign in to follow this  
hussam

crash in cvs client and 1.9.0 data update

Recommended Posts

I followed the intructions completely. I deleted maps, tiles and 3dobjects dirs and installed the update data then compiled the client from cvs.

whenever I kill something, the bag looks like it automatically poofed.

then when I use 'get all' to pick it up, I get a crash

gdb el.x86.linux.bin

GNU gdb (GDB) 7.0.1

Copyright © 2009 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law. Type "show copying"

and "show warranty" for details.

This GDB was configured as "i686-pc-linux-gnu".

For bug reporting instructions, please see:

<http://www.gnu.org/software/gdb/bugs/>...

Reading symbols from /home/hussam/packages/el/elc/el.x86.linux.bin...done.

(gdb) run

Starting program: /home/hussam/packages/el/elc/el.x86.linux.bin

[Thread debugging using libthread_db enabled]

[New Thread 0xa9827b70 (LWP 22383)]

[New Thread 0xa8f4cb70 (LWP 22384)]

[New Thread 0xa874bb70 (LWP 22385)]

[New Thread 0xa7f4ab70 (LWP 22386)]

 

Program received signal SIGSEGV, Segmentation fault.

0x08076819 in remove_bag (bag_id=0) at bags.c:293

293 ec_create_bag_pickup(objects_list[bag_list[bag_id].obj_3d_id]->x_pos, objects_list[bag_list[bag_id].obj_3d_id]->y_pos, objects_list[bag_list[bag_id].obj_3d_id]->z_pos, (poor_man ? 6 : 10));

(gdb) bt full

#0 0x08076819 in remove_bag (bag_id=0) at bags.c:293

snd = 158773880

#1 0x080dcd5e in process_message_from_server (in_data=0xa65004b8 "\035\002",

data_length=4) at multiplayer.c:1262

text_buf = "\177Not ready, this item still has a 59 cooldown.\000der in your EL installation a\001\000\000\000#\370\271\266Ј}\267o meЈ}\267\001", '\000' <repeats 11 times>, ",J\214\t\210\227\260\266\210H\214\t\020\365\213\t,J\214\t\000\000\000\000\030\202p\025", '\000' <repeats 28 times>, "X\a\214\t\001\000\000\000\270\266\200\t\000\000\000\000\000\000\000\000\376\000\000\000\000\001\001\000\000\000\002", '\000' <repeats 33 times>, "Q\000\000\000\004\000\000\000\001\002\357\276\003\000\000\000\006\000\000\000\000\024\000\000\000\000e\017\000\000\000\000\210H\214\t\000\020\000\000\000\000\000\000\000\000\000\000"...

#2 0x080ce6d0 in start_rendering () at main.c:170

message = 0xa6500498

event = {type = 24 '\030', active = {type = 24 '\030',

gain = 114 'r', state = 130 '\202'}, key = {type = 24 '\030',

which = 114 'r', state = 130 '\202', keysym = {

scancode = 1 '\001', sym = 168598752, mod = 3086965168,

unicode = 60895}}, motion = {type = 24 '\030', which = 114 'r',

state = 130 '\202', x = 1, y = 0, xrel = -25376, yrel = 2572},

button = {type = 24 '\030', which = 114 'r', button = 130 '\202',

state = 169 '\251', x = 1, y = 0}, jaxis = {type = 24 '\030',

---Type <return> to continue, or q <return> to quit---

which = 114 'r', axis = 130 '\202', value = 1}, jball = {

type = 24 '\030', which = 114 'r', ball = 130 '\202', xrel = 1,

yrel = 0}, jhat = {type = 24 '\030', which = 114 'r',

hat = 130 '\202', value = 169 '\251'}, jbutton = {

type = 24 '\030', which = 114 'r', button = 130 '\202',

state = 169 '\251'}, resize = {type = 24 '\030', w = 1,

h = 168598752}, expose = {type = 24 '\030'}, quit = {

type = 24 '\030'}, user = {type = 24 '\030', code = 1,

data1 = 0xa0c9ce0, data2 = 0xb7ff59b0}, syswm = {

type = 24 '\030', msg = 0x1}}

done = 0

network_thread_data = {0x9d745a0, 0x8441f3c}

last_frame_and_command_update = 168122

network_thread = 0xa06a258

message_queue = 0x9d745a0

#3 0x080ceb75 in main (argc=1, argv=0xbffff794) at main.c:348

No locals.

Edited by hussam

Share this post


Link to post
Share on other sites

I had a similar crash on one of the bag functions. I got the backtrace from gdb, but didn't have time to post it before coming to work. I'll post mine tonight too to see if it's exactly the same problem.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×