egghelp.org community

[iamdeath]

Hi, everything went fine but when I executed ./configure it gave me this error any idea what can I do best to solve it?

[nml375]

When you typed ./configure? Emmm...
Sure it was'nt when you tried to start your eggie?
_________________
NML_375, idling at #eggdrop@IrcNET

[iamdeath]

errr.. when I typed ./eggdrop -m config.file then I recived that error. Sorry that was a wrong quote earlier excuse me for that.
_________________
|AmDeAtH @ Undernet

Death is only the *Beginning*...

[nml375]

Ah well, in any case, that message really does'nt say much more than that you encountered a segment violation when running your eggdrop.

Without a stack backtrace on a coredump (as specified in the bug-report file), there really is'nt much to be done...
_________________
NML_375, idling at #eggdrop@IrcNET

[iamdeath]

So that'sa server issue, need admin to be informed right?
_________________
|AmDeAtH @ Undernet

Death is only the *Beginning*...

[nml375]

Nope, might just be a plain, simple bug in eggdrop..
_________________
NML_375, idling at #eggdrop@IrcNET

[rosc2112]

Is this on a SunOS box? Seen this error before under SunOS, beyond that I can't offer more info, except perhaps to check around egghead's site for bug reports/patches to fix it.

[nml375]

This error could be pretty much anything. Without a proper backtrace on a coredump, there is'nt even enough information to make an educated guess what the error is.

All we find out from this, is that some time prior the crash (possibly not even related to the crash whatsoever), the function init_bind in src/tclhash.c was executed and completed. We do not have any information on what took place afterwards, and thus led up to the actual crash.

Make sure you get a coredump when your eggie crashes ('ulimit -c 10000' should do the trick if it otherwize won't dump a core),
locate the coredump file,
read the bug-report document!!
follow the instructions at paragraph 4.8 in the above mentioned file,
post the output from that.

Then we just might have a chance on figuring this one out...
_________________
NML_375, idling at #eggdrop@IrcNET

[iamdeath]

[DragnLord]

grab a different tarball from http://www.eggheads.org/downloads/ and see if the error persists across versions

the contents of config.log may shed some light on this

since your shell is on a GNU system, this may be the result of the shell provider installing TCL via RPM instead of source

[nml375]

it's ulimit, not unlimit.. also, that should only be needed if your eggie does not dump a core upon crash.. running 'ulimit -c' should reveal the current limit for coredumps (as long as it does'nt return 0, your eggie should produce a core, but allowing larger cores, such as 10megs, may be helpful).

The problem, very simply, is that there is a bug in the source that causes a segment violation (accessing unallocated memory, etc). Getting a coredump and doing a backtrace reveals where the actual segment violation occured, along with calls leading up to that point. Which is exactly the information needed to even have a chance at doing an educated guess on what the problem is...

Your system seems to be running a fairly recent and stable kernel. SMP-support should'nt be much of an issue, although newer releases of Fedora Core (such as FC5) does tend to cause some issues with eggies and similar - usually due to the use of threaded tcl.
_________________
NML_375, idling at #eggdrop@IrcNET

[iamdeath]

I deleted the directory again the .tar file and the eggdrop directory.. I removed everysingle thing and downloaded with every new file now its working .. I dont know what was the issue.. but thank you for your kind help I really appreciate that.

Thanks once again

iamdeath
_________________
|AmDeAtH @ Undernet

Death is only the *Beginning*...