egghelp/eggheads community

New to the module world. Need help.

2002-11-13T06:00:41-04:00

YES!!!!! Finally, I got it to work! Thank you all for you help. Indeed, I was overlooking parts.

UmbraSG, who will probably have more questions soon enough

Statistics: Posted by UmbraSG — Wed Nov 13, 2002 6:00 am

New to the module world. Need help.

2002-11-12T03:00:11-04:00

Okay, going to give it a shot. Had computer problems, so it's a good thing I posted the code Ended up having to build an entirly new system and wipe the harddrives. God, don't you just love it when everything goes wrong all at once ?

Umby

Statistics: Posted by UmbraSG — Tue Nov 12, 2002 3:00 am

New to the module world. Need help.

2002-11-08T13:21:15-04:00

First of all, 'buffer' is a single char. You need to read into nArray!

Also, if you're doing this on linux, you can use gdb to find out exactly what is happening. Follow the directions to make a debug-enabled eggdrop ('make debug'). Then when it crashes, you should have a core file in the bot's dir... like core.1234 (pid). You should then type (in the bot's dir):

gdb eggdrop core.1234

It will start, read in 'symbol information,' and then tell you exactly where the bot crashed. If it doesn't, type "where" and it will show you. There are really advanced things you can do with it... I can't explain them all here, but probably the most useful is to use the "up" command to go up the backtrace to your function (it will tell you which function it is in at each step... use "down" if you went too far up) and then use "print " and you can see the values of all your variables at the time of the crash. It's really handy.

Another useful thing is to start eggdrop, and then type

gdb eggdrop -p 1234 (your pid)

Gdb will attach to eggdrop and let you debug it while it's actually running. You can set a breakpoint ("break " command) at the function that is crashing and then use "step" to go line-by-line until it crashes.

Statistics: Posted by stdragon — Fri Nov 08, 2002 1:21 pm

New to the module world. Need help.

2002-10-28T08:49:31-04:00

You didnt read my second post did you?

The error is there ... look up there.

Dont do a make static - that means that the modules are no longer dynamically loaded. Do a make clean then a make debug (i think - check the compiling docs - there are lots of docs in the release, not just source!!!)

alos, I wasnt talking about typing the command into dcc, I was talking about having a dcc connection to the console open at the time, and watching for putlogs (its a function - and its used in woobie - as I said before, if you have your console level set right, you will see the putlogs appear in the dcc chat - its a lot like old skool printf debugging. except with a bigger cache problem )

and yes - ppslim is right - context is your friend - that and the docs folder in the distribution - all of this is explained in there!!!

Statistics: Posted by Photon — Mon Oct 28, 2002 8:49 am

New to the module world. Need help.

2002-10-28T06:38:47-04:00

The reason it shows the line "Context;" as the error point, is becuase it is designed to.

"Context;" is a debug marker. Everytime this macro is called, it stors the filename, and line number. Thus, whe your bot crashes, it tells you the last time the "Context;" macro was called.

This can be used, to tell, near enough (if used properly) where the error is.

The error you have, will be located between the line number shown in the last content message, and the next context.

Thus, if you place more "Context;" lines in, youw ill soon find out, exactly where the error is.

Statistics: Posted by ppslim — Mon Oct 28, 2002 6:38 am

New to the module world. Need help.

2002-10-28T03:52:47-04:00

ARGH!! So frutrated! A friend suggested that I do 'make static' which still caused me to have a Segment Violation error on a line that contain 'Context;' Honestly, i have felt like throwing my computer to the floor and stomping on it. woobie works without any problems what-so-ever, but if I had one line to woobie, suddenly the code no longer works.

Statistics: Posted by UmbraSG — Mon Oct 28, 2002 3:52 am

New to the module world. Need help.

2002-10-25T15:57:42-04:00

Answer to #1: No dccing into the bot to type the command. I type it in the room. Yes, I have got a segment violation, but that one is with the compiled form. I have never got the one I compiled to work (dns module won't compile either because of no functional resolvers). It gave me a tcl?.h error ('?' - don't remember the whole name). It told me to report it as a bug since it was a segment violation.

Answer to Question #2: I haven't used Context nor putlog.

Answer to Question #3: I don't think so. How would I go about defining debug mode?

Ok .. here comes the fun part .. debugging.
step 1 - are you dcc'ed into the bot when you run the command? Does it give a segment violation?

step 2 - have you used Context; and putlog to trace the line where it crashes? If you have your console mode set right, you can view the putlogs as they happen, and the last Context; call (along with a small history of previous calls) will be reported if the bot crashes. Believe me, its easy if the bot crashes - if it goes into an infinate loop, its much moer fun!!

step 3 - is the bot compiled in debug mode? If so you wall have extensive memory allocation info, and if the bot crashes, it will do a core dump, which you can run a debugger over (more detail in another thread not too far down on this forum)

Statistics: Posted by UmbraSG — Fri Oct 25, 2002 3:57 pm

New to the module world. Need help.

2002-10-25T06:38:25-04:00

oh and btw - in pub_rules, I suspect

Code:

char nArray[25]

should be

Code:

char nArray[255]

as you are freading 255 bytes into it ...

and why are you noticing the user text one char at a time?

Statistics: Posted by Photon — Fri Oct 25, 2002 6:38 am

New to the module world. Need help.

2002-10-25T04:55:34-04:00

Ok .. here comes the fun part .. debugging.

step 1 - are you dcc'ed into the bot when you run the command? Does it give a segment violation?

step 2 - have you used Context; and putlog to trace the line where it crashes? If you have your console mode set right, you can view the putlogs as they happen, and the last Context; call (along with a small history of previous calls) will be reported if the bot crashes. Believe me, its easy if the bot crashes - if it goes into an infinate loop, its much moer fun!!

step 3 - is the bot compiled in debug mode? If so you wall have extensive memory allocation info, and if the bot crashes, it will do a core dump, which you can run a debugger over (more detail in another thread not too far down on this forum)

Statistics: Posted by Photon — Fri Oct 25, 2002 4:55 am

New to the module world. Need help.

2002-10-25T01:12:44-04:00

Okay, here's the new problem

::[ 10:10:46 pm]:: !rules
::[ 10:10:47 pm]:: * Quits: Succubus (~MoToKo@kami.click-network.com) (Read error: Connection reset by peer)

I have not a clue what's causing this.

Statistics: Posted by UmbraSG — Fri Oct 25, 2002 1:12 am

New to the module world. Need help.

2002-10-24T16:16:07-04:00

Ah Cool!! Thank you all. I will give them a try immediately. I got it to run now, however it crashes when I type the ! like !ax or !rules. Otherwise, it works fine doing nothing =P

Kevin P.

Statistics: Posted by UmbraSG — Thu Oct 24, 2002 4:16 pm

New to the module world. Need help.

2002-10-24T08:18:39-04:00

You'll also need to replace

Code:

static Function *global = NULL;

with

Code:

static Function *global = NULL, *irc_funcs = NULL;

in order for the irc function table to be imported correctly.

Wcc

Statistics: Posted by Wcc — Thu Oct 24, 2002 8:18 am

New to the module world. Need help.

2002-10-23T07:27:01-04:00

Oh - one more thing.

You should really be module_depending on all the modules you are using - and noticably you are depending on the irc module already (and possibly server - havent read the code fully)

And on the end of the pub table stick a {0, 0, 0, 0} instead of {0} - its safer.

Statistics: Posted by Photon — Wed Oct 23, 2002 7:27 am

New to the module world. Need help.

2002-10-23T07:24:04-04:00

Yeh .. its your #includes ... code is shared from one mod to another via menas of a function table and #defs. Therefore if your include files are not right then it wont work. Dont know why its not complaining about header file not found tho.

It should be

Code:

#include "../module.h"#include "../irc.mod/irc.h"#include "../server.mod/server.h"#include "../channels.mod/channels.h"#include "OneOfMyHeaders.h"

I have to admit it took a while to get something running with the first module I wrote, but press on ... the real fun starts when you get bugs and of course have no debugger .. *sigh*

Statistics: Posted by Photon — Wed Oct 23, 2002 7:24 am

New to the module world. Need help.

2002-10-22T19:14:14-04:00

I aint too good when it comes to C, but the directories used in the #include statments are out of whack.

Statistics: Posted by ppslim — Tue Oct 22, 2002 7:14 pm