Logs2HTML Error on Windrop...

[rileyil77]

This is weird... I was using an older version of Log2Html with WinDrop. Then got to looking for a fix for the Alice.TCL and found on one page that Logs2Html module had been updated. So, I decided to update it....
Then I got this error:

Module loaded: logs2html (with lang support)
9 [sig] eggdrop 3736 open_stackdumpfile: Dumping stack trace to eggdrop.exe.stackdump

I was just wondering if anyone had a fix for this? I saw on another forum site, that it was suggested to WinDrop users to downgrade to eggDrop v1.6.17, but I just had to upgrade due to an error in eggdrop v1.16.17 and an upgrade in WinXP SP3. The only downgrading I would do is to v1.6.19. Thanks for your help.

Again I'm using WinDrop...
eggdrop v1.6.20+checkconflags, on CYGWIN_NT-5.1 1.5.25(0.156/4/2)
WinXP Service Pack 3 with all the latest updates
1.5 Gig Ram

Thanks for any and all your help.

[nml375]

You could try compiling a new eggdrop along with alice and the alice-module in a cygwin environment.

[rileyil77]

This question is about Logs2Html, not an Alice issue.

[nml375]

Sorry, probably read the post to quickly and picked up on the alice fix in the first sentence. Nevertheless, your eggdrop is sent the no 9 signal, which I recall being the SIGSEGV signal (segment violation). Most likely, the module you downloaded was linked against an incompatible eggdrop build, or contains a bug.
Also, eggdrop uses a global table to pass functions to modules, so care must be taken to ensure that the table the module was linked with matches that of the eggdrop loading the module.

Building eggdrop and the module under the same environment would confirm or rule out the first.

You could use some debugger to read the coredump, as this cotains information on what your eggdrop was doing up until the crash. Other than that, you could only try various egdrop binaries until you find one that'll load your module..

[rileyil77]

So basically I have compile this module into a DLL for myself for my WinDrop. Not sound stupid or anything, but I've never really down that... How do I go about doing it?

Oh yeah... Here is the DUMP file it creates when my eggDrop (WinDrop) crashes:

Stack trace:
Frame Function Args
0022B5E8 7C802542 (000006AC, 0000EA60, 000000A4, 0022B630)
0022B708 61097F54 (00000000, 7C802600, 7C802542, 000000A4)
0022B7F8 61095AEB (00000000, 003B0023, 00230000, 0022CE68)
0022B858 61095FCB (0022B870, 00000000, 00000094, 61020C1B)
0022B918 61096182 (000004E4, 00000006, 0022B948, 61096383)
0022B928 610961AC (00000006, 0022CE88, 00000000, 00000000)
0022B948 61096383 (10155900, 00BA46A8, 10159398, 0022D008)
0022B9B8 610C3D58 (1010CF60, 00E47690, 00000001, 00000000)
0022B9D8 10094ACB (1010CF60, 0000012F, 0022BA48, 0000012B)
0022BA08 10094AF4 (1010CF60, 0022BA40, 0044FC4D, 00452360)
0022BAF8 00436573 (00000000, 1010CF60, 00000001, 101596B0)
0022BB38 0042ECEE (10126AF0, 1010CF60, 00000001, 0022BD30)
End of stack trace

That's from the stackdump file. Thanks again for your help everyone.

[nml375]

Well, since we're doing this under Windows, there's a few steps we'll have to take to get our build environment. There's a good guide here: http://www.eggheads.org/support/egghtml ... iling.html . The guide is written for eggdrop1.6.16, but you should be able to use 1.6.19 or latest cvs, just replace the 1.6.16 part with whatever version you've downloaded in the guide...

One thing worth mentioning, is that you'll also need "make" in addition to the list of needed packages. Also, the commands listed from step 2 and onwards are done in the cygwin shell (emulates a linux shell under windows), you should find an option for it under your start menu once step 1 is completed.

Once you've unpacked your eggdrop source in step 3, unpack your own module source into the src/mod/ directory.


The problem with raw coredump files, is that they contain no symbol names or such. That's why you need to run it through a debugger, that can translate the addresses into symbols by loading the application.