View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002036 | unreal | ircd | public | 2004-08-21 07:03 | 2004-09-04 04:12 |
| Reporter | fez | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2.1 | ||||
| Summary | 0002036: config hasher reports incorrect .dll when the file wasn't found... | ||||
| Description | alright, I've been playing around, and I noticed some people get errors like: loadmodule: : file not found. it inevitably has to do with the people being idiots and trying to load src/modules/commands.so on a win32 install, but I thought that it was weird that the name of the not-found dll was replaced by a weird char, then i did some investigating and found a few other little bugs in the "module not found" error checking routines: let's say that we have a valid module "modules/goodmodule.dll" and a module that doesn't exist called "modules/badmodule.dll" if the config looks like this: # snip start loadmodule "modules/goodmodule.dll"; loadmodule "modules/badmodule.dll"; # snip end then the config checker will report that goodmodule.dll could not be found, even though the error occured when trying to load badmodule.dll. Also, if there is no other module specified before the bad module, then it replaces the name of the module with a random char.... so there seems to be a little problem with a char* being incorrectly assigned in there somewhere. Also, I noticed that if I have: loadmodule "badmodule.dll"; it won't complain at all; it just skips over it, but if it's in a subdirectory: loadmodule "subdir/badmodule.dll"; then that's when it will start to complain. So, there you have a few bugs to work out with the hashing routines..... have fun -- fez | ||||
| 3rd party modules | |||||
|
|
About the "weird chars" problem: it is already fixed in CVS. From the Changes file: <QUOTE> ** 3.2.1 release ** - Fixed a win32 module problem where file not found errors would display random characters, reported by STING </QUOTE> |
|
|
As far as I know, every one of these is the exact same bug, and they were all fixed by the change that AngryWolf mentioned. I tried each and every one of your cases, and they all worked fine. |
|
|
Already fixed. |
