hmmm, i seem to remember someone on another mud i used to work on pointing that
one out as well, tho i've never seen it affect my own mud... i don't think it
would have anything to do with send_to_char or write_to_buffer, but with the
act_new function, since it parses for $'s, if you use act statements in your
various globals like gossip and whatnot, and someone were to gossip $p blah,
then in theory act should parse that out and try to match it up to an obj
variable that was passed as an argument, only since that act statement probably
looked something like this:
act(buf,ch,NULL,vch,TO_CHAR);
then it would be parsing that $p and trying to relate it to the NULL variable
you passed, which is where the obj variable would be, and it's trying to access
obj->short_descr, and since obj = NULL, *crash*... having not had to deal with
that on my own mud, i'm not quite sure of what the fix for it may be, but now
that you know what's most likely causing it, you can maybe take a crack at it
from there :)
wavewave
Richard Lindsey.
-----Original Message-----
From: Rick St Jean [mailto:[EMAIL PROTECTED]
Sent: Tue 9/14/2004 11:09 AM
To: [email protected]
Cc:
Subject: send to char bug
Hey all,
I had someone pop on my mud a few months ago and tell me about a
bug in send_to_char. It had to do with the write_to_buffer function.
This person used a $p in global communications string and crashed
things.
I am not able to duplicate it .., and I was told to use sprintf in the
send_to_char
function, but I cannot locate anything related to this bug or a fix.
Anyone know what this person was talking about?
Thanks.
Rick
--
ROM mailing list
[email protected]
http://www.rom.org/cgi-bin/mailman/listinfo/rom
