> I ran into a similar bug in my own code. I traced it to StrNCopy. It places > a null byte at n+1 (!!!) if the source string is N bytes long (ie, the > source string is longger than N). This is where N is the last parameter. I just glanced through the 3.0 src and verified that StrNCopy works correctly. Could this have been a problem in pre-3.0 systems? > I bet that NegLibGetHostName does something like: > StrNCopy(dest, hostName, sizeof(dest)); I don't think so. There aren't any strings involved in moving those bits around, they're all pointers and longs. It's really seems like an issue of the array termination. The rom must loop to that max constant, but the array is declared too small for that to work right. Sanjay (on behalf of Craig) Scrawl
