Constant segfaults with db.c

  • Kolvek
  • Topic Author
  • Offline
  • New Member
  • New Member
More
6 years 3 months ago - 6 years 3 months ago #5351 by Kolvek
Constant segfaults with db.c was created by Kolvek
I deleted all the objects in my mud except for the fireball, in zone 0. However, I can't seem to load it (load obj 2), or use it in any commands within zedit. Despite this, it appears in the olist and I can edit it with oedit. When I shutdown the mud, the object is delete from circle-3.5/lib/world/obj/0.obj. It's quite odd, and I can't seem to fix it.

Fixed - I had deleted part of spec_assign that wasn't tampering with existing items, so I brought it back. Now I get a segmentation fault to do with

db.c:2842
2842 if ((obj_index + mid)->vnum == vnum)

Anyone with the same issue?
Last edit: 6 years 3 months ago by Kolvek.

Please Log in or Create an account to join the conversation.

More
6 years 3 months ago #5352 by thomas
Replied by thomas on topic Constant segfaults with db.c
I think the code was never tested with only one object. Even if it ought to work.

That line is number 3594 in the latest version on github:
github.com/tbamud/tbamud/blob/master/src/db.c#L3594

Is it possible for you to upgrade to the latest version (3.5 is relatively long time ago)

Please Log in or Create an account to join the conversation.

More
6 years 3 months ago #5360 by Kyle
Replied by Kyle on topic Constant segfaults with db.c
This is a bug with 3.5. I distinctly remember ripping my hair out over it thinking it was something I had caused. Rhade ended up noticing the problem first.

It crashes when it tries to calculate 'mid'.

Please Log in or Create an account to join the conversation.

Time to create page: 0.084 seconds