Segmentation fault when building kdelibs

On 19 Sep 2005 16:17:03 -0400, Lowell Gilbert
<freebsd-questions-localbe-well.ilk.org> wrote:
> Pat Maddox <pergesugmail.com> writes:
> 
> > I'm trying to upgrade my system, and the build of
kdelibs always fails
> > because of some segmentation fault.  I have
absolutely no idea what
> > all this means, so I'll try to post as much of the
error as I can
> > determine is relevant.  Hopefully somebody can
help me out.
> >
> > In file included from kjanuswidget.cpp:24:
> > /usr/X11R6/include/qheader.h:207: internal
compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/b
ugs.html> for instructions.
> > gmake[3]: *** [kjanuswidget.lo] Error 1
> > gmake[3]: Leaving directory
`/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui'
> > gmake[2]: *** [all-recursive] Error 1
> > gmake[2]: Leaving directory
`/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui'
> > gmake[1]: *** [all-recursive] Error 1
> > gmake[1]: Leaving directory
`/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2'
> > gmake: *** [all] Error 2
> > *** Error code 2
> >
> > Stop in /usr/ports/x11/kdelibs3.
> > ** Command failed [exit code 1]: /usr/bin/script
-qa
> > /tmp/portupgrade31298.0 make
> > ** Fix the problem and try again.
> > ** Listing the failed packages (*:skipped /
!:failed)
> >         ! x11/kdelibs3 (kdelibs-3.4.0_1)       
(segmentation fault)
> > --->  Packages processed: 0 done, 0 ignored, 0
skipped and 1 failed
> 
> The obvious question is: does it always fail at the
same point?  If
> not, then it's almost certainly a hardware problem.  If
it does, then
> a bit more information on your system would be needed,
including how
> you updated the ports skeletons, and whether you tried
updating them
> again since you first saw the problem.  And if you
aren't already, try
> using the system compiler to build the port.
> 

I've had a couple people suggest that it may be a hardware
problem -
what should I be looking for?
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote:
>> The obvious question is: does it always fail at the
same point?  If
>> not, then it's almost certainly a hardware problem.
 If it does, then
>> a bit more information on your system would be
needed, including how
>> you updated the ports skeletons, and whether you
tried updating them
>> again since you first saw the problem.  And if you
aren't already,  
>> try
>> using the system compiler to build the port.
>
> I've had a couple people suggest that it may be a
hardware problem -
> what should I be looking for?

Pretty much what was quoted above.  

If you run the same build twice, does the compiler crash at
the same  
place, or in a different place?  If the crash happens
somewhere else  
each time, it's probably hardware.

-- 
-Chuck

_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On 9/19/05, Charles Swiger <cswigermac.com> wrote:
> On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote:
> >> The obvious question is: does it always fail
at the same point?  If
> >> not, then it's almost certainly a hardware
problem.  If it does, then
> >> a bit more information on your system would be
needed, including how
> >> you updated the ports skeletons, and whether
you tried updating them
> >> again since you first saw the problem.  And if
you aren't already,
> >> try
> >> using the system compiler to build the port.
> >
> > I've had a couple people suggest that it may be a
hardware problem -
> > what should I be looking for?
> 
> Pretty much what was quoted above.  
> 
> If you run the same build twice, does the compiler
crash at the same
> place, or in a different place?  If the crash happens
somewhere else
> each time, it's probably hardware.
> 
> --
> -Chuck
> 
> 

Happens in different spots, so I guess it's a hardware
problem.  But
what exactly am I looking for?  Is it bad ram, a bad disk? 
How do I
find out what's messed up?
_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Sep 19, 2005, at 6:16 PM, Pat Maddox wrote:
> Happens in different spots, so I guess it's a hardware
problem.  But
> what exactly am I looking for?  Is it bad ram, a bad
disk?  How do I
> find out what's messed up?

CPU cooling or bad memory are likely culprits.

Run memtest.org's checker overnight and see what that finds.
 memtest  
is also available as a port, I think, but I burned the .iso
image  
they have and use that as a standalone bootable checker.  If
you have  
name-brand hardware, people like Dell and whatnot offer a
diagnostics  
floppy or CD which can do useful testing, too...

-- 
-Chuck

_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"