View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001891 | unreal | documentation | public | 2004-06-22 00:33 | 2004-06-22 09:54 |
| Reporter | w00t | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0001891: tre.dll crashes wircd.exe with 3.2Final | ||||
| Description | Ok, all's fine and good. I downloaded Unreal3.2 final, to upgrade my rather buggy and dilapidated Unreal3.2-b18 installation. All went well, and the compile (under VS.NET) went smoothly. The problems came on startup, after copying tre.dll from\src\win32 to \. "UnrealIRCd has encountered a fatal error. Debugging information has been dumped to wircd.1512.core..." You know the rest. Looking at the core file interested me quite a bit... ===================== File: wircd.1512.core ===================== Generated at Mon Jun 21 14:08:25 2004 Windows XP (5.1.2600) Unreal3.2[FinWXOoE] (1.1.1.1.2.16 2004/04/24 23:53:42) ----------------- Memory Information: Physical: (Available:327MB/Total:511MB) Virtual: (Available:2018MB/Total:2047MB) ----------------- Exception: Access Violation ----------------- Backup Buffer: ----------------- Registers: EAX=0x00000030 EBX=0x00d35ee8 ECX=0x00b425d0 EDX=0x00b436f0 ESI=0x16803b00 EDI=0x00b425d0 EIP=0x100038a2 EBP=0x00b42058 ESP=0x0012f87c ----------------- Stack Trace: Module: tre #0 (null):0: ===================== EoF ===================== Interesting... so it was tre causing the problems. Off I traipse to my Unreal3.2b18 folder... I copy b18's version of tre.dll to 3.2's folder. It starts without a hitch... | ||||
| 3rd party modules | |||||
|
|
See http://www.vulnscan.org/UnrealIrcd/faq/#70 :p Also, there was a similar bug which has been fixed in CVS. |
