segmentation fault eggdrop1.6.13

Darmoth · Post by **Darmoth** » Thu Nov 28, 2002 2:50 pm

Hi,

I have a weird problem, I successfully installed the 1.6.13 on 2 servers and it's running fine. On one other shell I can extract the archive, but if I start ./configure all I get is a segmentation fault.
When I tried to compile the 1.6.12 again, it worked without any problems.

Any Ideas what could cause this segmentation fault ?

ppslim · Post by **ppslim** » Thu Nov 28, 2002 4:36 pm

No - but the exact error message can heklp a lot.

Darmoth · Post by **Darmoth** » Sat Nov 30, 2002 2:15 pm

Hi ppslim,

lol, you'll not belive it, but the exact error message is really just "segmentation fault".

I untar the archive, change into eggdrop1.6.13 and than it looks like this:

./configure
segmentation fault

and I'm back on the promt. I have really seen a bunch of errors since I started with eggdrops, but this irs really new to me

ppslim · Post by **ppslim** » Sat Nov 30, 2002 6:14 pm

This is a segmentation fault caused by somthing happening in the "./configure" script.

It may not actualy be the script, but a program it is calling.

After a quick look about, there is nothing I can sugest to fix it. However, you can take a look at the file "config.log" and see how far the script actualy got, before it broke.

It is most likely a system issue.

According to the CVS server, there has been 4 changes made between 1.6.12 and 1.6.13, two of these being made due to updated versions of autoconf, one minor change for Mac OSX and to revert a previously applied patch.

From this, you may like tryign to run the command "autoconf" before typing "./configure".

Darmoth · Post by **Darmoth** » Sun Dec 01, 2002 11:02 am

Thanks ppslim,

I'll give it a try and run autoconf 1st.
And yes, I think the problem is caused by the shell. Unfortunally, but not unexpected, the support didn't answer my mail yet

).

Mo-Ize · Post by **Mo-Ize** » Sun Dec 01, 2002 11:29 am

I hope for you that it's not /bin/sh which segfaults ...
In such a case, you should contact the shell admins ...

Darmoth · Post by **Darmoth** » Wed Dec 04, 2002 3:38 am

I don't think it's the bin/sh.
I still think it's a problem with the setup at that shell and some changes in the configure script.
I gave it another try, the same problem. Than I replaced the configure script with the script from the 1.6.12 archive and voila, everything worked fine and smoothly as with all my bots before. May be if I have a bit more time I'll compare the scripts. But since I had no problems with the 1.6.13 on some other shells and my own server, it's hard to say what exactly the problem is.

ppslim · Post by **ppslim** » Wed Dec 04, 2002 7:18 am

One sugestion I would make, is to try downloading 1.6.12, running "autoconf" then ./configure.

If this fails, it's combination of your shell and updates to the ./configure script.

If it works fine, then it can be safly said it's the ./configure script included, and updates that have been made.

mariusm · Post by **mariusm** » Sun May 04, 2003 1:38 pm

FYI:

When I do ./configure for 1.6.13 I get "Segmentation Fault".
When I do ./configure for 1.6.12 everything works fine.

ppslim · Post by **ppslim** » Mon May 05, 2003 12:17 pm

Then try 1.6.15

www.geteggdrop.com

1.6.14 was a dud, so that is why there was a jump.

Darmoth · Post by **Darmoth** » Wed May 07, 2003 4:41 am

Heh, I just tried that

But with the same result, ./configure runs in a segmentationfault with 1.6.15 again.
I got the 1.6.13 running when I used the configure script from 1.6.12, the last version I could compile on that shell without any problems.
Unfortunally this workaround don't work this time.
As with 1.6.13 I could compile the 1.6.15 on my other shells as well as on my BSD machines without any problems, so i suppose the problem is the shell, not the eggdrop.
Well, have o wait if their support will be so kind to answer my mail

ppslim · Post by **ppslim** » Wed May 07, 2003 4:47 am

While not directly related to this issue.

You could try stating the scripting using

Code: Select all

bash configure

or

Code: Select all

sh configure

Darmoth · Post by **Darmoth** » Wed May 07, 2003 6:57 am

Thanks ppslim, I tried that as well, found it in the eggdrops documentation. But it didn't help.

Well, they moved my shellaccount on an other server and voila, compiling the eggie was run as smooth as it can be

.
The techie think it's either an incompatible library or a missing perl module.

ppslim · Post by **ppslim** » Wed May 07, 2003 7:36 am

A missing perl module?? Dunno where he got that one from, seeing as there is no relation to perl.

Darmoth · Post by **Darmoth** » Wed May 07, 2003 8:06 am

Lol, don't ask me where he got the perl module idea from.
I guess they just have a problem with some libraries on that server.

egghelp/eggheads community

segmentation fault eggdrop1.6.13

segmentation fault eggdrop1.6.13

I have this too