[<a href='17753.html'>Next Message in Time</a>] | 
[<a href='17751.html'>Previous Message in Time</a>] | 
[<a href='17761.html'>Next Message in Topic</a>] | 
[<a href='17749.html'>Previous Message in Topic</a>] <br/><br/>
<b>Message ID:</b> 17752 <br/>
<b>Date:</b> Thu Apr 13 19:31:33 BST 2000 <br/>
<b>Author:</b> Perhaps a Princess... <br/>
<b>Subject:</b> RE: [eqbards] Lavastorm bug <br/>
<br/><br/>
<div id="ygrps-yiv-358857838"><blockquote><span title="ireply">&gt;-----Original Message-----<br/>
&gt;From: Benjamin Jerrad Segal [mailto:<a rel="nofollow" target="_blank" href="mailto:birdman@...">birdman@...</a>]<br/>
&gt;Sent: Thursday, April 13, 2000 11:15 AM<br/>
<br/>
&gt;On Thu, 13 Apr 2000, Bill Costlow wrote:<br/>
<br/>
&gt;&gt; Last night when my party zoned into Lavastorm from<br/>
&gt;&gt; Najena our druid was teleported into a lava pool in<br/>
&gt;&gt; the far North side of the zone.<br/>
<br/>
&gt;This is a well-known bug, being teleported into lava somewhere beneath a<br/>
&gt;lava pool (therefore not being able to surface).  Why it hasn&#39;t been fixed<br/>
&gt;is beyond me, it would certainly take a load off the guides&#39; time.<br/>
<br/>
 </span></blockquote>My guess? They are having a hard time pinning down what exactly in the<br/>
code is causing this to happen.<br/>
<br/>
First, they have to have a set of circumstances that causes it to ALWAYS<br/>
happen. So they can run through them over and over, figuring out where their<br/>
code is messing things up. Go through line by line.<br/>
<br/>
A problem that happens occasionally can be a LOT more difficult to pin down.<br/>
Even when I know my users are having problems, in a much smaller program<br/>
I work on, it can take me a week or more to find where the problem is,<br/>
going line by line and trying to figure out why the code doesn&#39;t do what<br/>
it seems to be saying The problem could even end up being in entirely<br/>
different<br/>
code that just tangentially affects.<br/>
<br/>
Sarah Heacock</div>