most likely the where cmd is sprintf'ing to a string which isnt big enough
to hold all the stuff put in it.
just increase the size of your string buffer and you should be okay.
Patrick Dughi wrote:
> Something I've noticed, but have yet to have the time to fix - I
> get an odd crash when I do a 'where' as an immortal.
>
> The odd thing is that the command 'where b' for example will
> consistently crash the mud, whereas another like 'where ba' will not.
> I've checked for null strings on the objects and the sort, but this was
> not the case... Add to this the odd core I get:
>
> #0 0x8058cab in perform_immort_where (ch=0x20202020,
> arg=0x20202020 <Address 0x20202020 out of bounds>)
> at act.informative.c:3010
> 3010 if (CAN_SEE_OBJ(ch, k) && isname(arg, k->name) &&
> (gdb) bt
> #0 0x8058cab in perform_immort_where (ch=0x20202020,
> arg=0x20202020 <Address 0x20202020 out of bounds>)
> at act.informative.c:3010
> #1 0x20202020 in ?? ()
> (gdb) quit
>
> Obviously its overwriting memory somewhere (as opposed to trying
> to do a string comparison or the like on a null string), but where, I
> cannot see. Aside from actually sitting down and debugging it for real,
> anyone seen this before, or have any ideas?
>
> PjD
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
> +------------------------------------------------------------+
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST