On Wed, 13 Jun 2007 18:43:31 +0200
Laszlo Nagy [EMAIL PROTECTED] wrote:
Anders Troback wrote:
On Wed, 06 Jun 2007 20:06:52 +0200
Laszlo Nagy [EMAIL PROTECTED] wrote:
Jan Henrik Sylvester wrote:
[EMAIL PROTECTED] wrote:
On Tue, 5 Jun 2007, Jan Henrik Sylvester
Anders Troback wrote:
On Wed, 06 Jun 2007 20:06:52 +0200
Laszlo Nagy [EMAIL PROTECTED] wrote:
Jan Henrik Sylvester wrote:
[EMAIL PROTECTED] wrote:
On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote:
For me, rdesktop works -- I have all my ports upgraded...
On Wed, 06 Jun 2007 20:06:52 +0200
Laszlo Nagy [EMAIL PROTECTED] wrote:
Jan Henrik Sylvester wrote:
[EMAIL PROTECTED] wrote:
On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote:
For me, rdesktop works -- I have all my ports upgraded...
ldd `which rdesktop` says?
[EMAIL PROTECTED] wrote:
On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote:
For me, rdesktop works -- I have all my ports upgraded...
ldd `which rdesktop` says?
/usr/local/bin/rdesktop:
libcrypto.so.4 = /lib/libcrypto.so.4 (0x280a9000)
libX11.so.6 = /usr/local/lib/libX11.so.6
Jan Henrik Sylvester wrote:
[EMAIL PROTECTED] wrote:
On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote:
For me, rdesktop works -- I have all my ports upgraded...
ldd `which rdesktop` says?
/usr/local/bin/rdesktop:
libcrypto.so.4 = /lib/libcrypto.so.4 (0x280a9000)
libX11.so.6
updated
rdesktop application exits with segmentation fault (core dumped). I
also tried to install an older version from source (rdesktop 1.4.1) and
had the same result. Finally, I tried to run rdesktop but send its
output to a different machine (Ubuntu Feisty). It worked perfectly.
So I believe
For me, rdesktop works -- I have all my ports upgraded...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote:
For me, rdesktop works -- I have all my ports upgraded...
ldd `which rdesktop` says?
-Garrett
___
freebsd-questions@freebsd.org mailing list
the second command, using nvidia driver, caused a segmentation fault.
I suppose this error means I will not have OpenGL under the nv driver, but
there are other drawbacks of using these instead of the nvidia driver, so I
don't care. For instance, with the nv driver I get the desktop at most at
1/4
Sorry, in my previous answer didn't edit the subject.
On Thu, 24 May 2007 10:10:57 -0500, Derek Ragona wrote:
At 07:26 AM 5/24/2007, Ernest Sales wrote:
To celebrate te Xorg upgrade I got rid of all ports
installed in my system,
then did a fresh install. No problems building; well, I
To celebrate te Xorg upgrade I got rid of all ports installed in my system,
then did a fresh install. No problems building; well, I installed first
gnome-lite expecting it would pull the complete xorg meta-port and finally
had to install this to get all the stuff, but suppose this is harmless.
At 07:26 AM 5/24/2007, Ernest Sales wrote:
To celebrate te Xorg upgrade I got rid of all ports installed in my system,
then did a fresh install. No problems building; well, I installed first
gnome-lite expecting it would pull the complete xorg meta-port and finally
had to install this to get all
Ernest Sales wrote:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
found)
Are you loading the glx module in xorg.conf?
___
freebsd-questions@freebsd.org mailing list
as a segmentation fault with only
phpMyAdmin and then progressed, as I fiddled with config for
php4-extensions, to breaking php entirely. I too have a modded make.conf
file which I am about to change in accordance with this tip. However, to get
phpMyAdmin working again, take a look
Terry,
Just solved my php / roundcube problems by removing -funroll-loops
from my CFLAGS in /etc/make.conf. Now I just have CFLAGS= -O2 -pipe
Recollection:
5.2.0 -march=pentium3m -O2 -pipe -funroll-loops Fail
5.2.0 -march=pentium3 -O -pipe Success
5.2.1
I've just had the phpMyAdmin not starting problem after making changes to
php.ini and adding extensions. It began as a segmentation fault with only
phpMyAdmin and then progressed, as I fiddled with config for
php4-extensions, to breaking php entirely. I too have a modded make.conf
file which I am
Gerard,
I completed steps 1 through 6 that you suggested below. Step 6 took
two whole days to complete. I had to babysit the blue screens of config.
Sorry to say it still does the exact same thing. httpd seg faults
with no core file whenever the phpMyAdmin/index.php web page is browsed.
Spil,
Looks like you are seeing the same thing that I am.
Terry Todd
On Mon, Feb 12, 2007 at 01:31:15PM +0100, Spil Oss wrote:
There were definately SEGV
From http-error.log
[Mon Feb 12 11:18:32 2007] [notice] child pid 23075 exit signal
Segmentation fault (11)
[Mon Feb 12 11:18:32
On Tuesday February 13, 2007 at 06:13:41 (AM) Terry Todd wrote:
I completed steps 1 through 6 that you suggested below. Step 6 took
two whole days to complete. I had to babysit the blue screens of config.
Sorry to say it still does the exact same thing. httpd seg faults
with no core
*.core
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal
Segmentation fault (11)
I am out of ideas on what to try next. Anyone else have any
suggestions?
Can you try unmounting
Segmentation fault (11)
I am out of ideas on what to try next. Anyone else have any
suggestions?
Can you try unmounting and fsck'ing the partition (fsck -f
/dev/adXsYz)
where url_generating.lib.php lives?
I thought by creating a new url_generating.lib.php file
] child pid 8512 exit
signal Segmentation fault (11)
I am out of ideas on what to try next. Anyone else have any
suggestions?
Can you try unmounting and fsck'ing the partition (fsck -f
/dev/adXsYz)
where url_generating.lib.php lives?
I thought by creating a new
there is no core file I have checked with find / -name
*.core
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal
Segmentation fault (11)
I am out of ideas on what to try next
.
When I say there is no core file I have checked with find / -name *.core
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal
Segmentation fault (11)
I am out of ideas on what to try next
2007] [notice] child pid 8512 exit signal Segmentation
fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
Can you try unmounting and fsck'ing the partition (fsck -f /dev/adXsYz)
where url_generating.lib.php lives?
I thought by creating a new
checked with find / -name *.core
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal Segmentation
fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
Can you try
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal
Segmentation fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
Can you try unmounting and fsck'ing
I have checked with find / -name *.core
and there are no core files anywhere on the system.
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal
Segmentation fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
Can you
] child pid 8512 exit signal Segmentation
fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
Can you try unmounting and fsck'ing the partition (fsck -f /dev/adXsYz)
where url_generating.lib.php lives?
Given that the error you are seeing is so repeatable
/messages file gets:
Feb 3 16:07:38 testbox kernel: pid 8512 (httpd), uid 80: exited on signal 11
/var/log/httpd-errors gets:
[Sat Feb 3 16:07:39 2007] [notice] child pid 8512 exit signal Segmentation
fault (11)
I am out of ideas on what to try next. Anyone else have any suggestions?
TIA,
Terry
note that everything else is working fine : xfce-4.4, anjuta,
firefox, etc...
FreeBSD 7.0-CURRENT #6: Fri Feb 2 13:47:26 EST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYSMP i386
running gdb kile :
Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 100060]
0x29d0f1f9
note that everything else is working fine : xfce-4.4, anjuta,
firefox, etc...
FreeBSD 7.0-CURRENT #6: Fri Feb 2 13:47:26 EST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYSMP i386
running gdb kile :
Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 100060]
0x29d0f1f9
On Wed, 27 Dec 2006, Garrett Cooper wrote:
ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and
tor here always exit with signal 11 and Segmentation fault
message.
Hmmm... doesn't look like you have any bad options.. You should try
compiling the port with the debug flag (-g
Hello.
Does anybody there have experience how to run an ports/security/tor ?
I have use FreeBSD 4.11-RELEASE-p13 and tor here always exit with
signal 11 and Segmentation fault message.
--
dima 7509107*mail,ru 2:550/112
___
freebsd-questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dima wrote:
Hello.
Does anybody there have experience how to run an ports/security/tor ?
I have use FreeBSD 4.11-RELEASE-p13 and tor here always exit with
signal 11 and Segmentation fault message.
--
dima 7509107*mail,ru 2:550/112
Could
On Wed, 27 Dec 2006, Garrett Cooper wrote:
Does anybody there have experience how to run an
ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and tor
here always exit with signal 11 and Segmentation fault message.
Could you provide your make.conf settings, in particular your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dima wrote:
On Wed, 27 Dec 2006, Garrett Cooper wrote:
Does anybody there have experience how to run an
ports/security/tor ? I have use FreeBSD 4.11-RELEASE-p13 and tor
here always exit with signal 11 and Segmentation fault message.
Could
this:
[EMAIL PROTECTED] ~]# smbpasswd -a admin
New SMB password:
Retype new SMB password:
Unable to open/create TDB passwd
Unable to open/create TDB passwd
pdb_getsampwnam: TDB passwd (/usr/local/private/passdb.tdb) did not exist.
File successfully created.
Segmentation fault: 11 (core dumped
) did not
exist. File successfully created.
Segmentation fault: 11 (core dumped)
Then it gives this:
[EMAIL PROTECTED] ~]# smbpasswd -a admin
New SMB password:
Retype new SMB password:
Unable to open/create TDB passwd
pdb_getsampwnam: Unable to open TDB passwd
(/usr/local/private
successfully created.
Segmentation fault: 11 (core dumped)
Then it gives this:
[EMAIL PROTECTED] ~]# smbpasswd -a admin
New SMB password:
Retype new SMB password:
Unable to open/create TDB passwd
pdb_getsampwnam: Unable to open TDB passwd
(/usr/local/private/passdb.tdb)! account_policy_get
] ~]# smbpasswd -a admin
New SMB password:
Retype new SMB password:
Unable to open/create TDB passwd
Unable to open/create TDB passwd
pdb_getsampwnam: TDB passwd (/usr/local/private/passdb.tdb) did not exist.
File successfully created.
Segmentation fault: 11 (core dumped)
Then it gives this:
[EMAIL PROTECTED
.
Type pear help shortcuts to list all command shortcuts.
Type pear help command to get the help for the specified command.
Segmentation Fault in 42156, waiting for debugger
I have no idea what could cause the problem and much less, how to
troubleshoot it. Google hasn't been my friend, yet
Hi
I have some troubles with apache22
When I run phpinfo() I get a Segmentation fault (11)
apache-2.2.0_7
php5-5.1.2_1
php5-bz2-5.1.2_1
php5-calendar-5.1.2_1
php5-ctype-5.1.2_1
php5-dom-5.1.2_1
php5-filepro-5.1.2_1
php5-ftp-5.1.2_1
php5-gd-5.1.2_1
php5-gettext-5.1.2_1
php5-iconv-5.1.2_1
php5
Hi,
After upgrading to the newest Python 2.4.3, I always get a Segmentation
fault after running getmail using ssl connection. This problem doesn't
show up for ordinary pop3 connections without ssl. Is it related to the
the ssl library of freebsd?
By the way, I'm using freebsd6.0 and getmail
On Sun, Apr 02, 2006 at 03:56:27PM -0700, Andrew Reitz wrote:
Can anyone supply any hints as to how I can get more debugging
information (I don't see any core files anywhere), and/or how I can
fix this problem?
In /usr/local/etc/php/extensions.ini, try enabling/disabling modules,
whilst
On Sun, Apr 02, 2006 at 08:02:12PM -0400, RJ wrote:
When I have setup a server I use php4-4.4.2_1,
mysql-server-4.1.18_2, php4-extensions-1.0 and apache.
And when you tell the php4-extensions configuration screen that you want
MySQL support, by checking the knob, it installs php4-mysql.
. By itself, Apache is working fine spitting out static
pages. However, whenever I try to load a page that needs to go
through the PHP interpreter, I get a segmentation fault:
nr:/usr/local/etc# tail /var/log/httpd-error.log
[Sun Apr 02 15:54:47 2006] [notice] Graceful restart requested, doing
-
From: Andrew Reitz [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Sent: Sunday, April 02, 2006 6:56 PM
Subject: FreeBSD 6-STABLE: Apache 2.2 and php 4.4 segmentation fault
Hello,
I am a long time FreeBSD user of FreeBSD 4.x and Apache 1.3.x. I have
decided to get with the times, and upgrade
- Original Message -
From: RJ [EMAIL PROTECTED]
To: Andrew Reitz [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Sunday, April 02, 2006 8:02 PM
Subject: Re: FreeBSD 6-STABLE: Apache 2.2 and php 4.4 segmentation fault
Something doesn't seem right with those ports.
When I
On Apr 2, 2006, at 5:02 PM, RJ wrote:
Something doesn't seem right with those ports.
When I have setup a server I use php4-4.4.2_1, mysql-
server-4.1.18_2,
php4-extensions-1.0 and apache.
I think php4-4.4.2_1 and php4-mysql-4.4.2_1 will cause a conflict.
Some correct me if I'm
On Tuesday 21 February 2006 19:12, Lowell Gilbert wrote:
Ben Paley [EMAIL PROTECTED] writes:
me$ pkg_info | grep tar
gtar-1.15.1_1 GNU version of the traditional tar archiver
You're obviously not *using* gnu tar, because you would be getting
errors on the -l option if you were.
. But when I
put any links in, tar dies with a segmentation fault.
Has anyone got any ideas why?
No. I can't reproduce the problem here, using the system tar on
RELENG_6 (couple of weeks old).
___
freebsd-questions@freebsd.org mailing list
http
On Tuesday 21 February 2006 19:12, Lowell Gilbert wrote:
Ben Paley [EMAIL PROTECTED] writes:
Sorry. left off some information that might come in handy!
me$ uname -srm
FreeBSD 6.0-STABLE i386
me$ pkg_info | grep tar
gtar-1.15.1_1 GNU version of the traditional tar archiver
When source/usr/home/me/public_html is empty then it runs fine. But when I put
any links in, tar dies with a segmentation fault.
Has anyone got any ideas why?
Yup, looks like I'm using bsdtar
Now that you know which tar you're using, :-)
time to drag out the standard debugging process
From: Dieter [EMAIL PROTECTED]
Subject: Re: tar segmentation fault
To: freebsd-questions@freebsd.org
Message-ID: [EMAIL PROTECTED]
Now that you know which tar you're using, :-)
time to drag out the standard debugging process for
segmentation faults.
It's come to that, has it?
Oh well
/ -
Basically it's a collection of symlinks to stuff I want backed up. Then I run
tar -cLvy -f /usr/home/me/backup/backup.tar.bz2 /usr/home/me/backup/source/
When source/usr/home/me/public_html is empty then it runs fine. But when I put
any links in, tar dies with a segmentation fault.
Has anyone got any
-cLvy -f /usr/home/me/backup/backup.tar.bz2 /usr/home/me/backup/source/
When source/usr/home/me/public_html is empty then it runs fine. But when I
put any links in, tar dies with a segmentation fault.
Has anyone got any ideas why?
Thanks,
Ben
Hi all,
Yesterday I had trouble when configuring Apache 2.2 with PHP 4.4.2,
which caused Apache to crash (segmentation fault) when calling various
PHP functions.
The hint to the answer resided in the /var/log/httpd-error.log file:
And the /var/log/httpd-error.log file mentions
is that Apache 2.2 blows up (with a segmentation fault)
when calling various PHP scripts, which I think is due to a dodgy way of
having set-up PHP4 under Apache. This message works towards the issue,
providing relevant(?) details, as I type along:
Here we go:
Previously the machine was running
On 19 Sep 2005 16:17:03 -0400, Lowell Gilbert
[EMAIL PROTECTED] wrote:
Pat Maddox [EMAIL PROTECTED] 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
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
On 9/19/05, Charles Swiger [EMAIL PROTECTED] 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,
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
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
When I run portsnap update, I get the following error after it
extracts the files:
Building new INDEX files... Segmentation fault (core dumped)
This is occuring on three different machines, so I'm guessing it's a
problem with portsnap, not my one machine. But they all have similar
configurations
Hello,
On Sat, Sep 17, 2005 at 02:56:11PM -0600 or thereabouts, Pat Maddox wrote:
When I run portsnap update, I get the following error after it
extracts the files:
Building new INDEX files... Segmentation fault (core dumped)
This is occuring on three different machines, so I'm guessing
hudec [EMAIL PROTECTED] wrote:
Hello,
On Sat, Sep 17, 2005 at 02:56:11PM -0600 or thereabouts, Pat Maddox wrote:
When I run portsnap update, I get the following error after it
extracts the files:
Building new INDEX files... Segmentation fault (core dumped)
This is occuring on three
Pat Maddox wrote:
When I run portsnap update, I get the following error after it
extracts the files:
Building new INDEX files... Segmentation fault (core dumped)
Any ideas what's going on?
There is a bug in versions of portsnap prior to today which causes
make_index to core dump when
Hello,
MACHINE SPECS:
I'm running a SuperServer 6010H with 1 gi of memory and 1 gigahert cpu.
I'm getting an internal compiler error: Segmentation fault when doing a make
install clean of cvsup-without-gui.
I RUN THE FOLLOWING COMMANDS:
# cd /usr/ports/net/cvsup-without-gui/
# make install
Richard Crane wrote:
Hello,
MACHINE SPECS:
I'm running a SuperServer 6010H with 1 gi of memory and 1 gigahert cpu.
I'm getting an internal compiler error: Segmentation fault when doing
a make install clean of cvsup-without-gui.
I RUN THE FOLLOWING COMMANDS:
# cd /usr/ports/net/cvsup
On Fri, 12 Aug 2005 10:47:32 -0700
Garrett Cooper [EMAIL PROTECTED] wrote:
../../gcc/gcc/calls.c:1693: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
gmake[1
. My database is
MySQL 5.02.
The problem: when I attempt to open an index.php file
in the oscommerce program I get, in my httpd-error.log
[notice] child pid xxx exit signal Segmentation
fault(11)
All other php related sites are functioning well with
no problems. Do you believe this is being caused
. My database is
MySQL 5.02.
The problem: when I attempt to open an index.php file
in the oscommerce program I get, in my httpd-error.log
[notice] child pid xxx exit signal Segmentation
fault(11)
All other php related sites are functioning well with
no problems. Do you believe this is being caused
file
in the oscommerce program I get, in my httpd-error.log
[notice] child pid xxx exit signal Segmentation
fault(11)
All other php related sites are functioning well with
no problems. Do you believe this is being caused by
the code in the oscommerce program or something
FreeBSD is doing?
Thanks
to php4. Because of error
I've reinstalled Apache 1.3 and Perl5. My database is
MySQL 5.02.
The problem: when I attempt to open an index.php file
in the oscommerce program I get, in my httpd-error.log
[notice] child pid xxx exit signal Segmentation
fault(11)
All other php related sites
attempt to open an index.php file
in the oscommerce program I get, in my httpd-error.log
[notice] child pid xxx exit signal Segmentation
fault(11)
All other php related sites are functioning well with
no problems. Do you believe this is being caused by
the code in the oscommerce program or something
`Inappropriate file type or format'] [Updating the portsdb
format:bdb1_btree in /usr/ports ... - 11973 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
/portsdb.rb:587: [BUG] Segmentation fault
ruby 1.8.2 (2004-07-29) [i386-freebsd4]
Abort (core dumped)
i rebuilt the ports index by going to /usr/ports and doing make index,
but i still get this same deal.
whats up?
It helps if you read /usr/ports/UPDATING first :).
Kent
/site_ruby/1.8/portsdb.rb:587:
[BUG] Segmentation fault
ruby 1.8.2 (2004-07-29) [i386-freebsd4]
Abort (core dumped)
i rebuilt the ports index by going to /usr/ports and doing make index,
but i still get this same deal.
whats up?
You need to get into the habit of
1) Searching the archives
.. Done.
done
[Updating the portsdb format:bdb1_btree in /usr/ports ... - 11939 port
entries found
.1000.2000.3000.4000.5000
.6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587:
[BUG] Segmentation fault
ruby 1.8.2 (2004
Tabor Kelly wrote:
This has been discussed DOZENS of times on this list including TODAY.
What do you think the archives are for?!
Sorry, I will look harder. Like I said, I found a lot of people having
the problem (in the archives), I didn't find anyone explaining what
causes the problem or how
Hi:
I updated my source code to 4.10 and went to recompile world using
`make buildworld` and it prints this out:
gzip -cn /usr/src/usr.sbin/pccard/pccardd/pccard.conf.5 pccard.conf.5.gz
gzip -cn /usr/src/usr.sbin/pccard/pccardd/pccardd.8 pccardd.8.gz
Segmentation fault (core dumped)
*** Error
Segmentation fault (core dumped)
*** Error code 139
Stop in /usr/src/usr.sbin/pccard.
*** Error code 1
Stop in /usr/src/usr.sbin.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
35218#
Could someone tell me how to fix
I'm running FreeBSD 5.2.1 with X11 (KDE) and just did a make install
distclean for the limewire port in console.
Afterward, I typed exit to drop down from root to my local account. Then I
typed, limewire and got this:
bash-2.05b$ limewire
Segmentation fault
bash-2.05b$
Any ideas/suggestions
Malcolm Kay wrote:
On Friday 07 May 2004 06:42, Henrik W Lund wrote:
malloc() is your friend! :-)
-- double *ncost = malloc(sizeof (double) * persons * scens); --
This ought to do the trick. Just remember to make sure that malloc
returns a valid pointer, otherwise you'll have another seg
On Friday 07 May 2004 06:42, Henrik W Lund wrote:
malloc() is your friend! :-)
-- double *ncost = malloc(sizeof (double) * persons * scens); --
This ought to do the trick. Just remember to make sure that malloc
returns a valid pointer, otherwise you'll have another seg fault.
I'm
Hello,
This short program below represents a problem I am having with
segmentation faults in a much larger C program that has numerous
arrays. Seems as though when I increase the number of elements in an
array (here, for example, beyond 130,000) a seg fault occurs.
Any idea
This doesn't have much to do with FreeBSD, but...
On May 6, 2004, at 2:58 PM, Caroline Korves wrote:
Any idea on what I should change to make the program run with large
numbers of elements in my arrays?
Automatic variables get allocated from the stack, which can only grow
to handle 8 MB or so by
Subject:
segmentation fault-- is my array too long?
From:
Caroline Korves [EMAIL PROTECTED]
Date:
Thu, 06 May 2004 14:58:43 -0400
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
Hello,
This short program below represents
Subject:
segmentation fault-- is my array too long?
From:
Caroline Korves [EMAIL PROTECTED]
Date:
Thu, 06 May 2004 14:58:43 -0400
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
Hello,
This short program below represents
:
Segmentation fault (core dumped)
/stand/sysinstall worked fine by 2 days ago ...
What should i do?
Thank you!
_
Tired of spam? Get [2]advanced junk mail protection with MSN 8.
References
1. mailto:[EMAIL PROTECTED
Hi all,
this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
main() { time(); }
I don't have made important changes to the release except cosmetic ones. I'm
running the Linux compatibility module and have compiled with gcc 3.3.3. Any
ideas are welcome.
Abel
At 09:24 PM 3/21/2004, Abel Navarro wrote:
Hi all,
this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
main() { time(); }
Good for it! Seeing as time takes a pointer to a time_t, not passing it one
would use what ever happened to be on the stack as a pointer.
I don't have
Oops, you were rigth. I don't believe I have made such a mistake.
Thank you
Abel
On Mon, 22 Mar 2004 16:54, Chuck McManis wrote:
At 09:24 PM 3/21/2004, Abel Navarro wrote:
Hi all,
this program ends with a segmentation fault in a FreeBSD 5.1.2-RELEASE:
main() { time(); }
Good
signal
Segmentation fault (11)
LDAP entry:
# jlixfeld, Manager, ebit.ca
dn: uid=jlixfeld,cn=Manager,dc=domain,dc=tld
objectClass: uidObject
objectClass: simpleSecurityObject
objectClass: inetOrgPerson
uid: jlixfeld
cn: Manager
userPassword:: x
sn: Jason
anyone seen this before? any ideas
/ruby/site_ruby/1.8/pkgdb.rb:467: [BUG]
Segmentation fault
ruby 1.8.1 (2003-12-25) [i386-freebsd4]
Abort (core dumped)
dont' have the balls the mess with this stuff, so...any idea?
I assume you did the first step in UPDATING and did the pkg_delete step,
right? If so, you might try fixing up your
:
*any_file_that_changes.c or .h*: *number_that_changes*: compiler
error: segmentation fault
I've searched for information and people say that could be problems
with gcc or hardware (memory for eg.). I tried to install new version
of gcc (3.4.0) and still continues using the older (3.3.3), tried
/pkgdb.rb:467: [BUG]
Segmentation fault
ruby 1.8.1 (2003-12-25) [i386-freebsd4]
Abort (core dumped)
dont' have the balls the mess with this stuff, so...any idea?
Eureka!
Best regards
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
Hi,
I'm running 5.2.1 Release version of FreeBSD, gcc 3.3.3 and I'm
getting the same error when trying to compile JDK 1.4 from ports:
*any_file_that_changes.c or .h*: *number_that_changes*: compiler
error: segmentation fault
I've searched for information and people say that could be problems
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 05, 2004 22:11
Subject: ruby1.8 segmentation fault
Hi BSDers, I read the ports/UPDATING about ruby stuff and do
accordingly,
after reinstall portupgrade, I did portupgrade -fr
/usr/ports/land
101 - 200 of 211 matches
Mail list logo
