Re: Core dump with php52-recode?

[Greg Larkin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Richard Morse wrote:
 Hi! I just did a portsnap and found that php52 had been updated. When I 
 recompiled (using `portmaster -i php52 php52-extensions`, suddenly php 
 started crashing:
 
 Jun 9 10:27:30 hedwig kernel: pid 35517 (php), uid 1001: exited on signal 11 
 (core dumped) 
 
 I was able to trace this down to the php52-recode extension. Has anyone else 
 noticed this behaviour?
 
 Thanks,
 Ricky
 
 

Hi Ricky,

I ran into a similar problem a while back and corrected it by
re-ordering the PHP extensions.ini file.  Perhaps these pages will help
troubleshoot the problem:

http://nerdstock.org/php_extensions?lang=en
http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround

Hope that helps,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMD7I00sRouByUApARArYvAJoCtyHnjjr16X9aJ801+HazpGucJgCffQPN
tGah/ScE2ZIIcfylZnw2NGQ=
=q4IX
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Core dump

[Giorgos Keramidas]

On 2007-10-31 15:32, Rem P Roberti [EMAIL PROTECTED] wrote:
 A program that I use has started giving me this error message when I try
 to load it:

 Segmentation fault: 11 (core dumped)

 Can someone give me a heads up on what's going on here.  I've done a
 reinstall to no avail.

Is there any reason why you can't tell us the name of the program?

The more details you provide, the easier it is going to be for someone
else to help you troubleshoot the problem.

Do you have a debug-build of the program around?  If you do, you can use
gdb(1) to try to grab a stack trace of the program, and with a little
luck and a bit of effort, it may even be possible to find out the root
cause of the segmentation fault.

Giorgos

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core dump

[Roland Smith]

On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote:
 A program that I use has started giving me this error message when I try
 to load it:
 
 Segmentation fault: 11 (core dumped)

This means that the program has either tried to read from a part of the
memory that it isn't allowed to access, or it has tried to write to a
memory page that is marked read-only.
 
 Can someone give me a heads up on what's going on here.  I've done a
 reinstall to no avail.

It is a bug in the program.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpgQTPsLfEjo.pgp
Description: PGP signature

Re: Core dump

[Rem P Roberti]

On 2007.11.01 00:39:52 +, Roland Smith wrote:
 On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote:
  A program that I use has started giving me this error message when I try
  to load it:
  
  Segmentation fault: 11 (core dumped)
 
 This means that the program has either tried to read from a part of the
 memory that it isn't allowed to access, or it has tried to write to a
 memory page that is marked read-only.
  
  Can someone give me a heads up on what's going on here.  I've done a
  reinstall to no avail.
 
 It is a bug in the program.


Ok.  Well, the program is Fldigi, which is an amateur radio program, but
now Skype is doing the same thing.  Interestingly, Skype started dumping
core after I read UPDATING and made the changes suggested to get it
running correctly.

Rem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core dump

[cpghost]

On Thu, 1 Nov 2007 00:39:52 +0100
Roland Smith [EMAIL PROTECTED] wrote:

 On Wed, Oct 31, 2007 at 03:32:10PM -0700, Rem P Roberti wrote:
  A program that I use has started giving me this error message when
  I try to load it:
  
  Segmentation fault: 11 (core dumped)

Hey, it's Halloween! ;)

 This means that the program has either tried to read from a part of
 the memory that it isn't allowed to access, or it has tried to write
 to a memory page that is marked read-only.

Rem, if you have updated that program recently, you may have
installed a version that introduced a new bug.

It could also happen when one of the libraries loaded by
that program have been updated, and also introduced
such a bug (hint: ldd(1) for a list of dynamically
loaded libraries).

  Can someone give me a heads up on what's going on here.  I've done a
  reinstall to no avail.
 
 It is a bug in the program.

Yes, but if it doesn't always happen at the same location
of the program, or even starts to affect other programs,
seemingly randomly, you may also have a hardware problem,
like faulty RAM, overheating CPU, bad PSU etc... Check your
RAM with the ports sysutils/memtest86 and sysutils/memtest
if you have doubts.

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command in single user mode

[Lowell Gilbert]

Joe Auty [EMAIL PROTECTED] writes:

 I'm running 5.4. Perhaps restore is generating this particular error
 message? I don't know.

It would be hard to tell, without an intermediate disk to write the
data to so you can separate the dump from the restore.  You might be
able to trace one of the processes to see, but that requires a bit of
technical knowledge.

 I may have to go this route, see if I can put together the disk space
 to manage this. Is there a way to get tar to just extract directly to
 a destination directory so I don't have to contend with a single
 large tarball I need to create disk space for?

Sure.  As far as I'm concerned, that's the normal way to copy
directory trees.  You just pipe the output of the tar process into
another tar process that un-tars it in another place.  

E.g.:
tar -C ~/work/debugger -cf - . | tar -C temp -xf -



 
   My disk is over a 100 gigabytes, could this be what
  is causing dump to crap out?
 
  Could be.  Check your memory statistics while you're doing it, and see
  if you run out of VM.
 
 What is a good strategy for dealing with this possibility, should I
 go down that path?

Start by watching top(1) while it's running...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command SOLVED

[Joe Auty]

Thanks everybody for their help.

As it turns out, I guess dump was being starved for memory, as  
running it while booted into FreeBSD normally using -L to indicate a  
live filesystem worked just fine. I believe this is because there is  
an extra swap file available from a normal FreeBSD boot, as specified  
in my /etc/rc.conf. I'm not sure if my theory completely holds up,  
but there you have it.


Thanks again! I'm up and running...


On Feb 16, 2006, at 9:25 AM, Lowell Gilbert wrote:


Joe Auty [EMAIL PROTECTED] writes:


I'm running 5.4. Perhaps restore is generating this particular error
message? I don't know.


It would be hard to tell, without an intermediate disk to write the
data to so you can separate the dump from the restore.  You might be
able to trace one of the processes to see, but that requires a bit of
technical knowledge.


I may have to go this route, see if I can put together the disk space
to manage this. Is there a way to get tar to just extract directly to
a destination directory so I don't have to contend with a single
large tarball I need to create disk space for?


Sure.  As far as I'm concerned, that's the normal way to copy
directory trees.  You just pipe the output of the tar process into
another tar process that un-tars it in another place.

E.g.:
tar -C ~/work/debugger -cf - . | tar -C temp -xf -





 My disk is over a 100 gigabytes, could this be  
what

is causing dump to crap out?


Could be.  Check your memory statistics while you're doing it,  
and see

if you run out of VM.


What is a good strategy for dealing with this possibility, should I
go down that path?


Start by watching top(1) while it's running...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command SOLVED

[Joe Auty]

On Feb 16, 2006, at 9:52 AM, Giorgos Keramidas wrote:


On 2006-02-16 09:29, Joe Auty [EMAIL PROTECTED] wrote:

Thanks everybody for their help.

As it turns out, I guess dump was being starved for memory, as
running it while booted into FreeBSD normally using -L to indicate a
live filesystem worked just fine. I believe this is because there is
an extra swap file available from a normal FreeBSD boot, as specified
in my /etc/rc.conf. I'm not sure if my theory completely holds up,
but there you have it.

Thanks again! I'm up and running...


That's very likely.  I usually start single user mode with something
like the following:

# adjkerntz -i
# swapon -a
# fsck -p
# mount -u /
# mount -va

Having a swap partition enabled definitely helps to avoid ending up
without any free memory ;)





I was doing swapon -a too, but perhaps this command does not enable  
swap directories that have been attached to /etc/rc.conf?








---
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command SOLVED

[Giorgos Keramidas]

On 2006-02-16 09:29, Joe Auty [EMAIL PROTECTED] wrote:
 Thanks everybody for their help.

 As it turns out, I guess dump was being starved for memory, as
 running it while booted into FreeBSD normally using -L to indicate a
 live filesystem worked just fine. I believe this is because there is
 an extra swap file available from a normal FreeBSD boot, as specified
 in my /etc/rc.conf. I'm not sure if my theory completely holds up,
 but there you have it.

 Thanks again! I'm up and running...

That's very likely.  I usually start single user mode with something
like the following:

# adjkerntz -i
# swapon -a
# fsck -p
# mount -u /
# mount -va

Having a swap partition enabled definitely helps to avoid ending up
without any free memory ;)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command SOLVED

[Giorgos Keramidas]

On 2006-02-16 09:56, Joe Auty [EMAIL PROTECTED] wrote:
On Feb 16, 2006, at 9:52 AM, Giorgos Keramidas wrote:
On 2006-02-16 09:29, Joe Auty [EMAIL PROTECTED] wrote:
 Thanks everybody for their help.

 As it turns out, I guess dump was being starved for memory,
 as running it while booted into FreeBSD normally using -L to
 indicate a live filesystem worked just fine. I believe this
 is because there is an extra swap file available from a
 normal FreeBSD boot, as specified in my /etc/rc.conf. I'm not
 sure if my theory completely holds up, but there you have it.

 Thanks again! I'm up and running...

 That's very likely.  I usually start single user mode with
 something like the following:

 # adjkerntz -i
 # swapon -a
 # fsck -p
 # mount -u /
 # mount -va

 Having a swap partition enabled definitely helps to avoid
 ending up without any free memory ;)

 I was doing swapon -a too, but perhaps this command does not enable
 swap directories that have been attached to /etc/rc.conf?

It enables all partitions listed as 'swap' in /etc/fstab.  You
are probably using a `swapfile', instead of a swap partition, so
that wouldn't enable it, because the relevant file system may not
be mounted at the time you run 'swapon'.

This is one of the reasons behind my tendency to use a separate
swap partition instead of swapfile=foo in `/etc/rc.conf' :-/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command in single user mode

[Joe Auty]

On Feb 14, 2006, at 5:46 PM, Lowell Gilbert wrote:


Joe Auty [EMAIL PROTECTED] writes:


On Feb 14, 2006, at 9:08 AM, Lowell Gilbert wrote:


Joe Auty [EMAIL PROTECTED] writes:


Hello,

Following the instructions here: http://www.unixcities.com/howto/
index.html  I did a:

Those directions are a little outdated, but the problem is really  
just

that you didn't follow the directions closely enough:


dump -0f - /usr | restore -rf - /backup/usr


should have been more like

dump -0f - /usr | (cd /backup/usr;restore -xf - )



Okay, I'm still getting:


no space left in string table
abort?

If I say n, it just core dumps


Funny, I can't find that message in the source for dump at all.
The message, in -STABLE, is Do you want to abort dump?.

I also can't seem to find the string table error message, but I may
just have failed to search the right library so far.

Are you running something before 5.2?



I'm running 5.4. Perhaps restore is generating this particular error  
message? I don't know.




Any other suggestions?


Plenty.  If there are no special files (fifos, etc.) on the disk, any
archiver will do it.  e.g., tar(1)


   Would using dd be a valid workaround to
cloning my disk?


Sure.  If you really want a *clone* of the disk, it's a good option.
If having the same data files in the same filestructure would do, then
copying other attributes is overkill.


I may have to go this route, see if I can put together the disk space  
to manage this. Is there a way to get tar to just extract directly to  
a destination directory so I don't have to contend with a single  
large tarball I need to create disk space for?



 My disk is over a 100 gigabytes, could this be what
is causing dump to crap out?


Could be.  Check your memory statistics while you're doing it, and see
if you run out of VM.


What is a good strategy for dealing with this possibility, should I  
go down that path?










---
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command in single user mode

[Lowell Gilbert]

Joe Auty [EMAIL PROTECTED] writes:

 Hello,
 
 Following the instructions here: http://www.unixcities.com/howto/
 index.html  I did a:
 
Those directions are a little outdated, but the problem is really just
that you didn't follow the directions closely enough:

 dump -0f - /usr | restore -rf - /backup/usr

should have been more like

dump -0f - /usr | (cd /backup/usr;restore -xf - )
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command in single user mode

[Joe Auty]

On Feb 14, 2006, at 9:08 AM, Lowell Gilbert wrote:


Joe Auty [EMAIL PROTECTED] writes:


Hello,

Following the instructions here: http://www.unixcities.com/howto/
index.html  I did a:


Those directions are a little outdated, but the problem is really just
that you didn't follow the directions closely enough:


dump -0f - /usr | restore -rf - /backup/usr


should have been more like

dump -0f - /usr | (cd /backup/usr;restore -xf - )



Okay, I'm still getting:


no space left in string table
abort?

If I say n, it just core dumps


Any other suggestions? Would using dd be a valid workaround to  
cloning my disk? My disk is over a 100 gigabytes, could this be what  
is causing dump to crap out?








---
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump with dump command in single user mode

[Lowell Gilbert]

Joe Auty [EMAIL PROTECTED] writes:

 On Feb 14, 2006, at 9:08 AM, Lowell Gilbert wrote:
 
  Joe Auty [EMAIL PROTECTED] writes:
 
  Hello,
 
  Following the instructions here: http://www.unixcities.com/howto/
  index.html  I did a:
 
  Those directions are a little outdated, but the problem is really just
  that you didn't follow the directions closely enough:
 
  dump -0f - /usr | restore -rf - /backup/usr
 
  should have been more like
 
  dump -0f - /usr | (cd /backup/usr;restore -xf - )
 
 
 Okay, I'm still getting:
 
 
 no space left in string table
 abort?
 
 If I say n, it just core dumps

Funny, I can't find that message in the source for dump at all.  
The message, in -STABLE, is Do you want to abort dump?.

I also can't seem to find the string table error message, but I may
just have failed to search the right library so far.

Are you running something before 5.2?

 Any other suggestions?

Plenty.  If there are no special files (fifos, etc.) on the disk, any
archiver will do it.  e.g., tar(1)

Would using dd be a valid workaround to
 cloning my disk?

Sure.  If you really want a *clone* of the disk, it's a good option. 
If having the same data files in the same filestructure would do, then
copying other attributes is overkill.

  My disk is over a 100 gigabytes, could this be what
 is causing dump to crap out?

Could be.  Check your memory statistics while you're doing it, and see
if you run out of VM.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core Dump using portversion

[bsd]

Problem was due to multiple install of ruby that were not cleaned well.

solution :

de-install these various version and keep the last release of ruby.



Le 6 oct. 05 à 12:00, bsd a écrit :


This has not solved my issue :



ns2# pkgdb -fu
---  Updating the pkgdb
[Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 168  
packages found (-0  
+168) ... 
. 
 done]

ns2# portversion -l 
[Failed `Inappropriate file type or format'] [Updating the portsdb  
format:bdb1_btree in /usr/ports ... - 13568 port entries  
found .1000.2000...





The ruby process involved puts the processor at 98% use and nothing  
move on after that...


I had to kill the process in order to get my hand back on the  
server...


??




Le 6 oct. 05 à 11:31, Vladimir Tsvetkov a écrit :



We have one of our server that core dumps when we are trying to use
portversion




ns2# portversion -l 
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 168
packages found (-1 +1) (...). done]
[Failed `Inappropriate file type or format'] [Updating the portsdb
format:bdb1_btree in /usr/ports ... - 13568 port entries
found .1000.2000...[BUG] Segmentation fault
ruby 1.8.2 (2004-12-25) [i386-freebsd5]

Abort (core dumped)




So far I have :

- de-install and re-install ruby.
- de-install and re-install portupgrade.

Nothing has changed...


Our system is FreeBSD 5.2.1


Do you have any clue regarding the way we can solve this issue ??




This is from the portupgrade man page in the WARNING section:

Even if you don't do anything wrong, a package database may get
corrupt somehow when it is heavily updated. In such cases, run  
``pkgdb

-fu '' to rebuild the database and rescue the tools from coredumping.


Best Regards,
Vladimir







«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§

Gregober --- PGP ID -- 0x1BA3C2FD
bsd @at@ todoo.biz

«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions- 
[EMAIL PROTECTED]




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core Dump using portversion

[Andrew P.]

On 10/6/05, bsd [EMAIL PROTECTED] wrote:
 Hello,


 We have one of our server that core dumps when we are trying to use
 portversion

  ns2# portversion -l 
  [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 168
  packages found (-1 +1) (...). done]
  [Failed `Inappropriate file type or format'] [Updating the portsdb
  format:bdb1_btree in /usr/ports ... - 13568 port entries
  found .1000.2000...[BUG] Segmentation fault
  ruby 1.8.2 (2004-12-25) [i386-freebsd5]
 
  Abort (core dumped)

 So far I have :

 - de-install and re-install ruby.
 - de-install and re-install portupgrade.

 Nothing has changed...


 Our system is FreeBSD 5.2.1


 Do you have any clue regarding the way we can solve this issue ??


Try adding these lines to /usr/local/etc/pkgtools.conf, just
after other ENV's:

  ENV['PORTS_DBDRIVER'] = 'dbm_hash'
  ENV['PKG_DBDRIVER'] = 'dbm_hash'
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core Dump using portversion

[bsd]

This has not solved my issue :


ns2# pkgdb -fu
---  Updating the pkgdb
[Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 168  
packages found (-0  
+168)  
.. 
.. done]

ns2# portversion -l 
[Failed `Inappropriate file type or format'] [Updating the portsdb  
format:bdb1_btree in /usr/ports ... - 13568 port entries  
found .1000.2000...



The ruby process involved puts the processor at 98% use and nothing  
move on after that...


I had to kill the process in order to get my hand back on the server...

??




Le 6 oct. 05 à 11:31, Vladimir Tsvetkov a écrit :


We have one of our server that core dumps when we are trying to use
portversion



ns2# portversion -l 
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 168
packages found (-1 +1) (...). done]
[Failed `Inappropriate file type or format'] [Updating the portsdb
format:bdb1_btree in /usr/ports ... - 13568 port entries
found .1000.2000...[BUG] Segmentation fault
ruby 1.8.2 (2004-12-25) [i386-freebsd5]

Abort (core dumped)



So far I have :

- de-install and re-install ruby.
- de-install and re-install portupgrade.

Nothing has changed...


Our system is FreeBSD 5.2.1


Do you have any clue regarding the way we can solve this issue ??



This is from the portupgrade man page in the WARNING section:

Even if you don't do anything wrong, a package database may get
corrupt somehow when it is heavily updated. In such cases, run ``pkgdb
-fu '' to rebuild the database and rescue the tools from coredumping.


Best Regards,
Vladimir






«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§

Gregober --- PGP ID -- 0x1BA3C2FD
bsd @at@ todoo.biz

«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Core Dump not available

[Kris Kennaway]

On Tue, Dec 21, 2004 at 03:29:53AM +0530, Romil Shah wrote:
 
 
  Hi,
I am using the Adaptec aac 2200S controller , if the system crashes no 
 core dump is genertated. Is there any bug fixes for this , i am using old 
 FreeBSD version 4.5. I found some bug fixes in 5.0 ver of FreeBSD . So is 
 it possible to port this changes back to 4.5.

It may be possible, but I doubt you'll get any volunteers to do this
for you.

Instead you should verify that the bug isn't in your local
configuration.  Setting up crashdumps is documented in the handbook;
if you need more help, post more details about your system
configuration (i.e. what you've tried so far, and what errors you've
received).

Alternatively, if you're convinced this is an OS bug, you should
consider updating to a modern version of FreeBSD.

Kris


pgpmH86Fp01TJ.pgp
Description: PGP signature

Re: core dump with portupgrade

[Matthew Seaman]

On Sat, Sep 18, 2004 at 04:55:38PM -0500, Anthony Philipp wrote:
 Hello, when I was trying to upgrade my laptop with the latest ports this is what 
 happened. 
 
 
 
 (16:50:29) [EMAIL PROTECTED] /home/philipp1 1# portupgrade -arR
 Stale dependency: ORBit-0.5.17_1 -- gettext-0.12.1 -- manually run 'pkgdb -F' t
 o fix, or specify -O to force.
 (16:51:17) [EMAIL PROTECTED] /home/philipp1 2# pkgdb -F
 ---  Checking the package registry database
 Duplicated origin: textproc/expat2 - expat-1.95.6_1 expat-1.95.7
 Unregister any of them? [no] 
 Duplicated origin: databases/ruby-bdb1 - ruby-bdb1-0.2.1 ruby18-bdb1-0.2.2
 Unregister any of them? [no] yes
   Unregister ruby-bdb1-0.2.1 keeping the installed files intact? [no] yes
   - ruby18-bdb1-0.2.2 is kept.
   -- Saving the ruby-bdb1-0.2.1's +CONTENTS file as 
 /var/db/pkg/ruby18-bdb1-0.2.2/+CONTENTS.ruby-bdb1-0.2.1
   -- Unregistering ruby-bdb1-0.2.1
   -- Done.
 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 284 packages found (-1 
 +0) (...) done]
 Stale dependency: ORBit-0.5.17_1 - gettext-0.12.1 (devel/gettext):
 [Failed `Inappropriate file type or format'] [Updating the portsdb 
 format:bdb1_btree in /usr/ports ... - 11733 port entries found 
 .1000.2000.3000.4000.5000.../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587:
  [BUG] Segmentation fault
 ruby 1.8.2 (2004-07-29) [i386-freebsd5]
 
 Abort trap (core dumped)
 
 
 
 Also the same thing happened when I did portsdb -Uu or portversion -l 
 I can post those if required, and this is highly reproducible, so just ask if you 
 need more info.

You're not the only one to have been bitten by this.  Search the
archives for extensive mailing list traffic on this subject -- but in
short, a work around is:

# setenv PORTS_DBDDRIVER bdb1_hash

before you start running portsdb(1) or portupgrade(1).

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp05fHWWqQJp.pgp
Description: PGP signature

Re: core dump location

[Geert Hendrickx]

On Fri, Jul 02, 2004 at 06:14:28PM -0500, Chris wrote:
 *This message was transferred with a trial version of CommuniGate(tm)
 Pro*
 
 
 5.2.1-RELEASE
 
 
 I tried using this command to change the location where my core dump
 is being written:
 
 sysctl kern.corefile=/var/coredumps/%U/%N.core
 
 
 After doing that, new core dumps didn't show up there. I tried
 creating the directory (wasn't sure if it would be created with the
 first core dump or not) and chmod it to 0777 just to make sure it was
 writeable by any process - still no core dumps there.
 
 Is there a way to put it back the way it was, where the core dump ends
 up in the working directory as programname.core ?
 
 Thanks, Chris


I never touched it, so here's the default value: 

# sysctl kern.corefile
kern.corefile: %N.core

GH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: core dump

[Daniela]

On Saturday 08 March 2003 21:49, Thomas Haug wrote:

I had the same problem too.
The following shellscript helped (for csh):

while (1) 
 
make buildkernel KERNCONF=mykernel  make installkernel KERNCONF=mykernel  
break; 
 
end


 you're right there tim, it is changing the place in the compile that it
 bombs at each time, doing the same buildworld, with the same source !
 here some examples from NOW:

 PS: i did a memtest memtest 520m (let it run for ~30min) with NO
 errors AND i did a cpuburn burnP6 test for about ~15min with NO
 errors ?

 Server Hardware:

 Compaq Proliant ML310
 2x DDR 256MB, PC-2100 ECC Registered,266MHz, CL2.5
 Intel Pentium IV 2.4 GHz
 Compaq SMART-Array 221 SCSI RAID Controller with 3 hd's (3x 18GB == RAID5)


 1st try:
 -

 cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
 /usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.o
 cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
 /usr/src/lib/msun/src/s_nextafterf.c -o s_nextafterf.o
 cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
 /usr/src/lib/msun/src/s_rint.c -o s_rint.o
 cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
 /usr/src/lib/msun/src/s_rintf.c -o s_rintf.o
 cc: Internal compiler error: program cc1 got fatal signal 11
 *** Error code 1

 Stop in /usr/src/lib/msun.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 -bash-2.05b#

 -


 2nd try:
 -

 usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine
 -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN
 -DNO_IDEA  -c
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/conf/conf_mod.
c -o conf_mod.So
 cc: cpp0: Internal compiler error: program cc1 got fatal signal 4output
 pipe has been closed

 *** Error code 1

 Stop in /usr/src/secure/lib/libcrypto.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 -bash-2.05b#

 -


 3rd try:
 -

 cc -O -pipe  -DTERMIOS -DANSI_SOURCE
 -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl
 -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
 -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine
 -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN
 -DNO_IDEA  -c
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bool.c
 -o a_bool.o
 cc: Internal compiler error: program cc1 got fatal signal 11
 *** Error code 1

 Stop in /usr/src/secure/lib/libcrypto.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 *** Error code 1

 Stop in /usr/src.
 -bash-2.05b#

 -

 -bash-2.05b# tail -3 /var/log/messages
 Mar  8 21:25:13 ns1 /kernel: pid 28902 (cc1), uid 0: exited on signal 11
 (core dumped)
 Mar  8 21:40:35 ns1 /kernel: pid 63920 (cc1), uid 0: exited on signal 4
 (core dumped)
 Mar  8 21:48:11 ns1 /kernel: pid 92714 (cc1), uid 0: exited on signal 11
 (core dumped)
 -bash-2.05b#

 taxman wrote:
  On Friday 07 March 2003 04:00 pm, Thomas Haug wrote:
 Hi List members
 
 Since a few weeks my box is core dumping when i'm doing a make
 buildworld with
 one of the following error msgs (changing always :-)):
 
  If it is changing the place in the compile that it bombs at each time,
  doing the same buildworld, with the same source, then you have a *high*
  likelihood of hardware error of some sort.  Try doing the exact same
  buildworld two or three times in a row, does it bomb every time?  Same
  spot or different? You didn't show enough of the error to let us know
  that
  try using script to record the output of the build then you can include
  more of the error in your mail if needed.
 
 Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4
 (core
 dumped)
 Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11
 (core
 dumped)
 Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5
  (core dumped)
 
 This box is running since a year, so its pritty new and i never had
 problems
 with it. Every appl is running fine, nothing is core dumping, just the
  make buildworld does...
 
  That could easily be because buildworld stresses your system more and in
  different ways than most other apps.
 
  Tim

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

Re: core dump

[Thomas Haug]

wow that works :-) i just did a make buildkernel KERNCONF=mykernel and a 
make installkernel KERNCONF=mykernel == init 6

after that, make buildworld runs without any problems :-) thanx for 
helping !!

Thomas

Daniela wrote:
On Saturday 08 March 2003 21:49, Thomas Haug wrote:

I had the same problem too.
The following shellscript helped (for csh):
while (1) 
 
	make buildkernel KERNCONF=mykernel  make installkernel KERNCONF=mykernel  break; 
 
end



you're right there tim, it is changing the place in the compile that it
bombs at each time, doing the same buildworld, with the same source !
here some examples from NOW:
PS: i did a memtest memtest 520m (let it run for ~30min) with NO
errors AND i did a cpuburn burnP6 test for about ~15min with NO
errors ?
Server Hardware:

Compaq Proliant ML310
2x DDR 256MB, PC-2100 ECC Registered,266MHz, CL2.5
Intel Pentium IV 2.4 GHz
Compaq SMART-Array 221 SCSI RAID Controller with 3 hd's (3x 18GB == RAID5)
1st try:
-
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
/usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
/usr/src/lib/msun/src/s_nextafterf.c -o s_nextafterf.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
/usr/src/lib/msun/src/s_rint.c -o s_rint.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c
/usr/src/lib/msun/src/s_rintf.c -o s_rintf.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1
Stop in /usr/src/lib/msun.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

2nd try:
-
usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN
-DNO_IDEA  -c
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/conf/conf_mod.
c -o conf_mod.So
cc: cpp0: Internal compiler error: program cc1 got fatal signal 4output
pipe has been closed
*** Error code 1

Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

3rd try:
-
cc -O -pipe  -DTERMIOS -DANSI_SOURCE
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN
-DNO_IDEA  -c
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bool.c
-o a_bool.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1
Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

-bash-2.05b# tail -3 /var/log/messages
Mar  8 21:25:13 ns1 /kernel: pid 28902 (cc1), uid 0: exited on signal 11
(core dumped)
Mar  8 21:40:35 ns1 /kernel: pid 63920 (cc1), uid 0: exited on signal 4
(core dumped)
Mar  8 21:48:11 ns1 /kernel: pid 92714 (cc1), uid 0: exited on signal 11
(core dumped)
-bash-2.05b#
taxman wrote:

On Friday 07 March 2003 04:00 pm, Thomas Haug wrote:

Hi List members

Since a few weeks my box is core dumping when i'm doing a make
buildworld with
one of the following error msgs (changing always :-)):
If it is changing the place in the compile that it bombs at each time,
doing the same buildworld, with the same source, then you have a *high*
likelihood of hardware error of some sort.  Try doing the exact same
buildworld two or three times in a row, does it bomb every time?  Same
spot or different? You didn't show enough of the error to let us know
that
try using script to record the output of the build then you can include
more of the error in your mail if needed.

Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5
(core dumped)
This box is running since a year, so its pritty new and i never had
problems
with it. Every appl is running fine, nothing is core dumping, just the
make buildworld does...
That could easily be because buildworld stresses your system more and in
different ways than most other apps.
Tim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

Re: core dump

[Thomas Haug]

you're right there tim, it is changing the place in the compile that it 
bombs at each time, doing the same buildworld, with the same source ! 
here some examples from NOW:

PS: i did a memtest memtest 520m (let it run for ~30min) with NO 
errors AND i did a cpuburn burnP6 test for about ~15min with NO 
errors ?

Server Hardware:

Compaq Proliant ML310
2x DDR 256MB, PC-2100 ECC Registered,266MHz, CL2.5
Intel Pentium IV 2.4 GHz
Compaq SMART-Array 221 SCSI RAID Controller with 3 hd's (3x 18GB == RAID5)
1st try:
-
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c 
/usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c 
/usr/src/lib/msun/src/s_nextafterf.c -o s_nextafterf.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c 
/usr/src/lib/msun/src/s_rint.c -o s_rint.o
cc -O -pipe  -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_  -c 
/usr/src/lib/msun/src/s_rintf.c -o s_rintf.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1

Stop in /usr/src/lib/msun.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

2nd try:
-
usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine 
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN 
-DNO_IDEA  -c 
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/conf/conf_mod.c 
-o conf_mod.So
cc: cpp0: Internal compiler error: program cc1 got fatal signal 4output 
pipe has been closed

*** Error code 1

Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

3rd try:
-
cc -O -pipe  -DTERMIOS -DANSI_SOURCE 
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl 
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto 
-I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine 
-I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN 
-DNO_IDEA  -c 
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bool.c 
-o a_bool.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1

Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
-bash-2.05b#
-

-bash-2.05b# tail -3 /var/log/messages
Mar  8 21:25:13 ns1 /kernel: pid 28902 (cc1), uid 0: exited on signal 11 
(core dumped)
Mar  8 21:40:35 ns1 /kernel: pid 63920 (cc1), uid 0: exited on signal 4 
(core dumped)
Mar  8 21:48:11 ns1 /kernel: pid 92714 (cc1), uid 0: exited on signal 11 
(core dumped)
-bash-2.05b#



taxman wrote:
On Friday 07 March 2003 04:00 pm, Thomas Haug wrote:

Hi List members

Since a few weeks my box is core dumping when i'm doing a make
buildworld with
one of the following error msgs (changing always :-)):


If it is changing the place in the compile that it bombs at each time, doing 
the same buildworld, with the same source, then you have a *high* likelihood 
of hardware error of some sort.  Try doing the exact same buildworld two or 
three times in a row, does it bomb every time?  Same spot or different?
You didn't show enough of the error to let us know that
try using script to record the output of the build then you can include more 
of the error in your mail if needed.


Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5 (core
dumped)
This box is running since a year, so its pritty new and i never had
problems
with it. Every appl is running fine, nothing is core dumping, just the make
buildworld does...


That could easily be because buildworld stresses your system more and in 
different ways than most other apps.

Tim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

Re: core dump

[Bill Moran]

Thomas Haug wrote:
Hi List members

Since a few weeks my box is core dumping when i'm doing a make 
buildworld with
one of the following error msgs (changing always :-)):

Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4 
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11 
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5 (core
dumped)

This box is running since a year, so its pritty new and i never had 
problems
with it. Every appl is running fine, nothing is core dumping, just the make
buildworld does...
Sounds like hardware.  Install memtest and cpuburn and test the RAM and CPU.

--
Bill Moran
Potential Technologies
http://www.potentialtech.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

Re: core dump

[taxman]

On Friday 07 March 2003 04:00 pm, Thomas Haug wrote:
 Hi List members

 Since a few weeks my box is core dumping when i'm doing a make
 buildworld with
 one of the following error msgs (changing always :-)):

If it is changing the place in the compile that it bombs at each time, doing 
the same buildworld, with the same source, then you have a *high* likelihood 
of hardware error of some sort.  Try doing the exact same buildworld two or 
three times in a row, does it bomb every time?  Same spot or different?
You didn't show enough of the error to let us know that
try using script to record the output of the build then you can include more 
of the error in your mail if needed.

 Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4
 (core
 dumped)
 Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11
 (core
 dumped)
 Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5 (core
 dumped)

 This box is running since a year, so its pritty new and i never had
 problems
 with it. Every appl is running fine, nothing is core dumping, just the make
 buildworld does...

That could easily be because buildworld stresses your system more and in 
different ways than most other apps.

Tim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message