Shadow-4.1.4 segfaults on "pwconv"

Blender3D · 08-28-2010, 05:37 PM

Hello,

I've been compiling CLFS (SVN) with jhalfs (also SVN) a few times, and have gotten to step 152/186 with no problems. Suddenly, (I was tailing the logs), I get a segfault when the program "pwconv" is run. The compilation went smoothly.

I think this is because of my CLFAGS were a bit too much. They're

Code:

-march=native -O3

I changed them to

Code:

-march=native -O0

after experiencing these errors, but I get the same problem. Here is the result of "pwconv" ("passwd" runs with no problem) being run

Code:

Segmentation fault (core dumped)

It's not very descriptive...

Thanks for anybody who can help.

druuna · 08-29-2010, 05:22 AM

Hi,

CFLAGS could indeed be the underlying problem. Did you try unsetting them?

Maybe these articles might help you in setting safe CFLAGS:

Safe Cflags (gentoo wiki)
Safe Cflags/Intel (Do read the first warning!!)
Safe Cflags/AMD

I have Intel Core 2 Duo/Quad processors and use the following (which haven't given me any problems):

Quote:

CHOST="i686-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}"

Another thing: You do not mention this but are you also using MAKEFLAGS? This one does give me problems every so often (especially with make test/make check, but also on other occasions). I've decided to not use it any more.

Hope this helps.

Blender3D · 08-30-2010, 11:27 AM

Hmm, I tried using no CFLAGS, setting optimization to 0, removing march, etc. No idea.

I even modified the source code of the program to write a number after each call of a function. No luck...

druuna · 08-30-2010, 01:32 PM

Hi,

I've never played with/used jhalfs on clfs-svn, (b)lfs is my poison.....

Only advise I can give at this point is: Did everything go OK with both Cracklib and Linux-PAM (assuming you use these) and are you sure the Shadow package was build with (or without!!) these?

Hope this helps.

Blender3D · 08-30-2010, 06:14 PM

I tried to debug the problem, so I compiled "strace". Wow, that was REALLY useful.

It told me that there was a bad call to a file named "/etc/passwd". It does not exist. A quick "touch /etc/passwd" make the segfault go away.