IBM ViaVoice on Woody --> Always Segmentation Fault
Hi, We bought the IBM ViaVoice Speech Recognition software for Linux. To my surprise [maybe not ;-( ] it came in form of rpm files. So I used alien and everything installed perfictly fine/smoth - no problem. But then staring it ... The seems seems to use Java with some custom/binary java-modules. It just crashes with SegFault. We have a debian woody system and I also found out about the needed libstdc++2.9-glibc2.1 Then I tried all different kinds of java. (1.1.8 , 1.3, ibm-1.1.8, and now the 1.2.2 RC4 version from blackdown.org) I found at least one posting from Feb 17, 2002 on the emacspeak mailing list report success. But somehow I'm missing something here... Thanks, Sebastian Haase University of California, San Francisco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
25756 segmentation fault /usr/bin/dumpkeys
Hi,
after todays dist-upgrade on woody I lost my keyboard-configuration.
After dpkg-reconfigure console-common I get this error:
25756 segmentation fault /usr/bin/dumpkeys >${TMP}
No german keyboard anymore.
Any hints?
TIA
juh
--
Damit erhebt Heidegger das Sein zum alleinigen Autor aller
wesentlichen Briefe und setzt sich selbst als dessen aktuellen
Schriftführer ein. Wer in solcher Position redet, darf auch Stammeln
aufzeichnen und Schweigen publizieren. Sloterdijk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: diagnose segmentation fault with Mozilla 0.9.8-3 mailnews
On 2002.03.09 20:28 Paul Scott wrote: Can someone give suggestions for tracking down the segmentataion fault I get with Mozilla mailnews 0.9.8-3 which I also got with 0.9.8-2. The browser and the web page composer work fine. Someone at my local LUG knew this one. I hope it helps others. I believe the problem is in the preferences file. I renamed .mozilla and let Mozilla generate a new one and the segmentation faults are gone. Paul Scott
diagnose segmentation fault with Mozilla 0.9.8-3 mailnews
Can someone give suggestions for tracking down the segmentataion fault I get with Mozilla mailnews 0.9.8-3 which I also got with 0.9.8-2. The browser and the web page composer work fine. TIA, Paul Scott
Re: segmentation fault with kmail and attachements: what am I doing wrong?
On Fri, Jan 04, 2002 at 10:38:52AM +0100, rdiaz wrote: > Dear All, > > A few days ago I installed Woody (after a couple of years of suse). > Everything seems fine, but I am having a problem with Kmail (4:2.1.1-7). > It crashes as soon as I try to include an attachement (segmentation > fault, signal 11) in a new message. Same problem here. > I think I must be doing something stupid, since I have searched in this > list and the bug reports, and I cannot find anything similar. I have > tried a whole bunch of possible combinations: installing the full set of > kde packages (kdebase, konqueror, etc), installing only the required > libraries for kmail (kdelibs3 and kdebase-libs), purging and > reinstalling, etc, etc. Package installation (either from dselect or > directly using dpkg -i) aparently proceeds without problems, but still I > always get the segmentation fault when trying to include the > attachement, regardless of size and type of attachement. > > Can anybody suggest what I might try? Sorry, but I can confirm the buggy behaviour of kmail. kmail -v gives: Qt: 2.3.1 KDE: 2.2.2 KMail: 1.2 I have had testing and unstable in sources.list for apt, so it might be a unusual combination of versions. pgpqmMVtIDt31.pgp Description: PGP signature
segmentation fault with kmail and attachements: what am I doing wrong?
Dear All, A few days ago I installed Woody (after a couple of years of suse). Everything seems fine, but I am having a problem with Kmail (4:2.1.1-7). It crashes as soon as I try to include an attachement (segmentation fault, signal 11) in a new message. Moreover, in received messages that contain attachements it seems to think that attachements are URLs, not attachements (I am given the option of "open url" or "copy to clipboard", instead of the "save as", "open with", etc). I think I must be doing something stupid, since I have searched in this list and the bug reports, and I cannot find anything similar. I have tried a whole bunch of possible combinations: installing the full set of kde packages (kdebase, konqueror, etc), installing only the required libraries for kmail (kdelibs3 and kdebase-libs), purging and reinstalling, etc, etc. Package installation (either from dselect or directly using dpkg -i) aparently proceeds without problems, but still I always get the segmentation fault when trying to include the attachement, regardless of size and type of attachement. Can anybody suggest what I might try? Thanks, Ramón
Re: apt-get segmentation fault
> Some time ago I started and aborted an upgrade of some packages via FTP. Now
> everytime I try to install or update the list of available packages I get a
> Segmentation Fault. "dpkg --yet-to-unpack" shows that there are 89 packages
> marked for installation (many more than the five or six I really want to
> install), so I guess this problem is being caused by some inconsistency in the
> packages database. If so, is there any way to correct it?
>
> Until we meet again...
>
> Hélio Perroni Filho
>
Perhaps /var/lib/dpkg/{available,status} are corrupted and you need to
use the -old version?
--
Shaul Karl
email: shaulka(at-no-spam)bezeqint.net
Please replace (at-no-spam) with an at - @ - character.
(at-no-spam) is meant for unsolicitate mail senders only.
apt-get segmentation fault
Some time ago I started and aborted an upgrade of some packages via FTP. Now everytime I try to install or update the list of available packages I get a Segmentation Fault. "dpkg --yet-to-unpack" shows that there are 89 packages marked for installation (many more than the five or six I really want to install), so I guess this problem is being caused by some inconsistency in the packages database. If so, is there any way to correct it? Until we meet again... Hélio Perroni Filho
Re: Segmentation Fault w/ XF86Setup
Rafe B. wrote: I just tried to upgrade my "potato" box with XFree86 from "unstable." Bad idea? Not the best. This yields Segmentation Fault when I run XF86Setup. So my questions are: 1. Was it dumb to install XF86 4.1 on top of a 2.2r3 base (kernel 2.2.18pre21) ? Yes, if you mean installing XFree86 4.1 from unstable. No, if you used unofficial XFree86 4.1 packages for potato. Look at: http://lists.debian.org/debian-x/2001/debian-x-200109/msg00042.html 2. Is it possible that XF86Setup itself was somehow not updated? 3. Which deb contains XF86Setup? Danged if I can figure it out... xf86setup It is only found in potato. To configure XFree86 4.1, use dpkg-reconfigure xserver-xfree86 or XFree86 -configure 4. What's the minimim base for running XF86 version 4.1.0-9? Or is "apt-get" supposed to deal with such dependencies? Use apt-get or dselect to deal with dependencies. But there will probably so many upgraded packages to solve dependencies, you might as well install sid. 5. Suggestions on where to go from here... If I were you, I would consider either: 1. Reinstall potato packages you upgraded, and then install unofficial XFree86 4.1 packages for potato. or 2. Do a distribution upgrade to woody or sid. (There have been a number of messages in this list discussing the best way to do this.) I hope this helps. -- Jerome
Re: Segmentation Fault w/ XF86Setup
I just tried to upgrade my "potato" box with XFree86 from "unstable." Bad idea? Yes! This yields Segmentation Fault when I run XF86Setup. Mildly chaotic "update" process, since I was a bit confused about the Deb packages to get. I started with: xfree86-common x-window-system-core xserver-common .. at which point XF86Setup still ran, but showed no video boards to select from. Then I went and got: xserver-svga That is version 3.3.6-39 xserver-xfree86 libgnomesupport0 libgnomeui32 libgnome-perl // and finally: x-window-system version 4.1.x .. which is probably where I should have started. You have a mixture of 3.3.6 and 4.1 packages on your system So my questions are: 1. Was it dumb to install XF86 4.1 on top of a 2.2r3 base (kernel 2.2.18pre21) ? No but the wrong way of doing. Looks like you didn't even have a look on the packeges numbers. 2. Is it possible that XF86Setup itself was somehow not updated? XF86Setup is for 3.3.x 4. What's the minimim base for running XF86 version 4.1.0-9? Or is "apt-get" supposed to deal with such dependencies? apt-get is your choice. Go to http://people.debian.org/~bunk/ and read the instructions on how to install XF4 on potato with apt-get. 5. Suggestions on where to go from here... Whew! Many thanks in advance. I'm way over my head here, I guess . rafe b. Frank --
Segmentation Fault w/ XF86Setup
I just tried to upgrade my "potato" box with XFree86 from "unstable." Bad idea? This yields Segmentation Fault when I run XF86Setup. Mildly chaotic "update" process, since I was a bit confused about the Deb packages to get. I started with: xfree86-common x-window-system-core xserver-common .. at which point XF86Setup still ran, but showed no video boards to select from. Then I went and got: xserver-svga xserver-xfree86 libgnomesupport0 libgnomeui32 libgnome-perl // and finally: x-window-system .. which is probably where I should have started. This is on top of a plain vanilla 2.2r3 potato distro (does it matter?) The "old" 3.3.6 XFree86 worked just fine, but not on my new Matrox G-450 board. Oddly enough, running xdm or startx produces a valiant try... there, the report is: (EE) No devices detected Fatal server error: no screens found So my questions are: 1. Was it dumb to install XF86 4.1 on top of a 2.2r3 base (kernel 2.2.18pre21) ? 2. Is it possible that XF86Setup itself was somehow not updated? 3. Which deb contains XF86Setup? Danged if I can figure it out... 4. What's the minimim base for running XF86 version 4.1.0-9? Or is "apt-get" supposed to deal with such dependencies? 5. Suggestions on where to go from here... Whew! Many thanks in advance. I'm way over my head here, I guess . rafe b.
Re: Segmentation fault
On Mon, Oct 29, 2001 at 11:54:17PM +0100, Raffaele Sandrini wrote: > adding /usr/man to manpath > /usr/share/man is already in the manpath > /usr/X11R6/man is already in the manpath > /usr/local/man is already in the manpath > - [segfault] Hmm. The next thing man normally does after that is related to the current locale. Could you tell me what this outputs? echo LC_ALL=$LC_ALL echo LC_MESSAGES=$LC_MESSAGES echo LANG=$LANG echo LANGUAGE=$LANGUAGE I suspect add_nls_manpath() is buggy. Thanks, -- Colin Watson [EMAIL PROTECTED]
Re: Segmentation fault
> Hi Raffaele, > > If you tell me the version number of the man-db package you have > installed, I'll try to debug this. > > Thanks, I have version 2.3.20-6 of man-db installed. cheers, Raffaele -- Raffaele Sandrini <[EMAIL PROTECTED]> For encrypted Mail get my Public Key from "search.keyserver.net" ID: 0xEC4950E9
Re: Segmentation fault
On Mon, Oct 29, 2001 at 11:54:17PM +0100, Raffaele Sandrini wrote: > On Monday 29 October 2001 20:38, Karsten M. Self wrote: > > $ strace man foo > > Hi again, > > here the output of "strace man ls" [...] > and here the output of "man -d ls" Hi Raffaele, If you tell me the version number of the man-db package you have installed, I'll try to debug this. Thanks, -- Colin Watson [EMAIL PROTECTED]
Re: Segmentation fault
On Monday 29 October 2001 20:38, Karsten M. Self wrote:
> on Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini ([EMAIL
> PROTECTED])
wrote:
> > Hi,
> >
> > I can't use man anymore. On every manpage i get a segmentation fault.
> > Im using the 2.4.13-ac4 kernel.
> > any hints?
>
> $ strace man foo
Hi again,
here the output of "strace man ls"
-
open("/lib/libc.so.6", O_RDONLY)= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\270\327"..., 1024) =
1024
fstat64(0x3, 0xbfffedbc)= 0
old_mmap(NULL, 1187712, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001a000
mprotect(0x40132000, 40832, PROT_NONE) = 0
old_mmap(0x40132000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x117000) = 0x40132000
old_mmap(0x40138000, 16256, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40138000
close(3)= 0
open("/usr/local/qt3/lib/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/local/lib/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/opt/kde/lib/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("i686/mmx/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("i686/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("mmx/libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("libdb2.so.2", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/lib/libdb2.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0_\0\000"..., 1024) =
1024
fstat64(0x3, 0xbfffedac)= 0
old_mmap(NULL, 265836, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4013c000
mprotect(0x4017c000, 3692, PROT_NONE) = 0
old_mmap(0x4017c000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x3f000) = 0x4017c000
close(3)= 0
munmap(0x40016000, 14566) = 0
umask(022) = 022
brk(0) = 0x80635d4
brk(0x80635fc) = 0x80635fc
brk(0x8064000) = 0x8064000
fstat64(0, 0xb89c) = 0
fstat64(0x1, 0xb89c)= 0
fstat64(0x2, 0xb89c)= 0
getcwd("/root", 4094) = 6
SYS_199(0x40137058, 0, 0x40137d60, 0x40134e70, 0xb97c) = 6
semop(1075015768, 0x40134e70, 0)= 6
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=30, ws_col=80, ws_xpixel=0, ws_ypixel=0}) = 0
open("/root/.manpath", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/etc/manpath.config", O_RDONLY) = 3
fstat64(0x3, 0xbfffd49c)= 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40016000
read(3, "# manpath.config\n#\n# This file i"..., 4096) = 4096
read(3, "n the order listed here;\n# the d"..., 4096) = 570
read(3, "", 4096) = 0
close(3)= 0
munmap(0x40016000, 4096)= 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
rt_sigaction(SIGINT, {0x804e330, [INT], SA_RESTART|0x400}, {SIG_DFL}, 8) =
0
stat64(0x8063a08, 0xb724) = 0
stat64(0x8063a50, 0xb724) = -1 ENOENT (No such file or
directory)
stat64(0x80639b8, 0xb724) = -1 ENOENT (No such file or
directory)
stat64(0x8063928, 0xb724) = 0
stat64(0x8063ae8, 0xb724) = 0
stat64(0x8063ef0, 0xb714) = 0
stat64(0x8063ef0, 0xb724) = 0
stat64(0x8063ef0, 0xb714) = -1 ENOENT (No such file or
directory)
stat64(0x8063f30, 0xb714) = -1 ENOENT (No such file or
directory)
stat64(0x8063ef0, 0xb714) = 0
stat64(0x8063ef0, 0xb724) = 0
stat64(0x8063ef0, 0xb714) = -1 ENOENT (No such file or
directory)
stat64(0x8063ef0, 0xb714) = -1 ENOENT (No such file or
directory)
stat64(0x80639b8, 0xb724) = -1 ENOENT (No such file or
directory)
stat64(0x80637a0, 0xb724) = 0
brk(0x8065000) = 0x8065000
brk(0x8066000) = 0x8066000
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
and here the output of "man -d ls"
--
ruid=6, euid=6
++priv_drop_count = 1
>From the config file /etc/manpath.config:
Mandatory mandir `/usr/man'.
Mandatory mandir `/usr/share/man'.
Mandatory mandir `/usr
Re: Segmentation fault
On Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini wrote: > Hi, > > I can't use man anymore. On every manpage i get a segmentation fault. What version of man-db? Post the end of an strace (as Karsten said) as well as the output of 'man -d '. -- Colin Watson [EMAIL PROTECTED]
Re: Segmentation fault
on Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini ([EMAIL PROTECTED]) wrote: > Hi, > > I can't use man anymore. On every manpage i get a segmentation fault. > Im using the 2.4.13-ac4 kernel. > any hints? $ strace man foo Post the last hundred or so lines of output. *Not* the whole damned thing. Peace. -- Karsten M. Selfhttp://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? Home of the brave http://gestalt-system.sourceforge.net/ Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpQIDC8zBouk.pgp Description: PGP signature
Segmentation fault
Hi, I can't use man anymore. On every manpage i get a segmentation fault. Im using the 2.4.13-ac4 kernel. any hints? cheers, Raffaele -- Raffaele Sandrini <[EMAIL PROTECTED]> For encrypted Mail get my Public Key from "search.keyserver.net" ID: 0xEC4950E9
Re: slink segmentation fault
On Fri, 26 October 2001, Eduard Bloch wrote: > Many of these old 386 boxes have bad cheap memory chips. The time > passes, and after few years you memory errors like hell. It ran windows 3.1 ok when i got it - would this a microsoft quality hardware thing? Thanks for the help - Pete __ Get your free domain name and domain-based e-mail from Namezero.com New! Namezero Plus domains now available. Find out more at: http://www.namezero.com
Re: slink segmentation fault
#include Peter mcevoy wrote on Fri Oct 26, 2001 um 06:32:36AM: > Hi, > I have just put slink onto a 386 with 4meg of ram, installation went > well but i'm Many of these old 386 boxes have bad cheap memory chips. The time passes, and after few years you memory errors like hell. > navigate the filesystem but writing anything to disk gives me a > "segmentation fault". Sounds like bad RAM. Gruss/Regards, Eduard. -- Die 3 goldenen R's bei Microsoft Systemen: Retry, Reboot, Reinstall . (Joerg Schilling)
slink segmentation fault
Hi, I have just put slink onto a 386 with 4meg of ram, installation went well but i'm stuck on a particular problem now - when it asked me to set a root password for the first time, it seemed as though nothing was good enough - no matter what i put in it said "try again", occasionally it would say "password weak, type again to use anyway" but it would follow that with "try again". I'm able to login via tty2 and navigate the filesystem but writing anything to disk gives me a "segmentation fault". If anyone has any advice i'd be most appreciative, Thanks Pete __ Get your free domain name and domain-based e-mail from Namezero.com New! Namezero Plus domains now available. Find out more at: http://www.namezero.com
slink - segmentation fault
Hi, I have just put slink onto a 386 with 4meg of ram, installation went well but i'm stuck on a particular problem now - when it asked me to set a root password for the first time, it seemed as though nothing was good enough - no matter what i put in it said "try again", occasionally it would say "password weak, type again to use anyway" but it would follow that with "try again". I'm able to login via tty2 and navigate the filesystem but writing anything to disk gives me a "segmentation fault". If anyone has any advice i'd be most appreciative, Thanks Pete __ Get your free domain name and domain-based e-mail from Namezero.com New! Namezero Plus domains now available. Find out more at: http://www.namezero.com
Re: dpkg -i * gives segmentation fault
On Thu, Oct 25, 2001 at 05:35:25AM -0700, Hamma Scott wrote: > I was trying to upgrade to Woody. I've downloaded the > packages and did the following through instructions > (thank you by the way for all the help so far) > > # dpkg -i perl* Where are you? /var/cache/apt/archives ? This is last resort. This does not gurantee dependancies always. > I only had one package for perl (seemed a little odd). > I then tried to run: > # dpkg -i * This is even bolder. > After a bunch of output, I got a segmentation fault. Which package? Then install required package. Maybe libdb* > I then went through to try to upgrade libraries as I > was getting dependency problems and didn't know what > forcing the upgrade would do. > > Then, I thought the best thing to do is to do an > apt-get with dist-upgrade and --nodownload. I found > out that the apt-get must have been upgraded because > --nodownload is not recognized anymore. Maybe upgrade apt first. What is "apt-cache policy apt"? > I can run pon and apt-get, dpkg, vi, vim, but not > emacs right now. > Am I cooked? And what information would you need to > determine if I am? Just be paitient and fix problems one-by-one My quick-reference has some hint list to get out of situation like yours. http://www.aokiconsulting.com/quick/ Good luck. :-) > I'm considering using apt-get dselect-upgrade, is this > viable now? Well, I got till tonight. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
dpkg -i * gives segmentation fault
I was trying to upgrade to Woody. I've downloaded the packages and did the following through instructions (thank you by the way for all the help so far) # dpkg -i perl* I only had one package for perl (seemed a little odd). I then tried to run: # dpkg -i * After a bunch of output, I got a segmentation fault. I then went through to try to upgrade libraries as I was getting dependency problems and didn't know what forcing the upgrade would do. Then, I thought the best thing to do is to do an apt-get with dist-upgrade and --nodownload. I found out that the apt-get must have been upgraded because --nodownload is not recognized anymore. I can run pon and apt-get, dpkg, vi, vim, but not emacs right now. Am I cooked? And what information would you need to determine if I am? I'm considering using apt-get dselect-upgrade, is this viable now? Well, I got till tonight. Scott Hamma __ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
Re: segmentation fault??
> Hi, > > This is my first time to meet this message and don't know why. > The story is. > This afternoon, I tried to install ssh3 for higher security. > Follow standard step: > configure > make > make install > > everything was fine, no error message showed on the screen. > But, I can not connect to my server by ssh client server from poor win98. > (This is another problem >_<) For this problem (someone corrects me if I'm saying stupid things), you have to configure ssh with --with-apm option thus: ./configure --with-apm > So, I read FAQ. In FAQ said that I must check my ssh version, > use command "ssh -V ". I did it, and then showed "segmentation fault" on my > screen.. > Why??? Er... for this one... sorry :-( no idea Fred. > It is just simple command. > Hope someone can tell me why. Please!! *_* > And thanks for who read this mail.^^ > > haheho > > > >
segmentation fault??
Hi, This is my first time to meet this message and don't know why. The story is. This afternoon, I tried to install ssh3 for higher security. Follow standard step: configure make make install everything was fine, no error message showed on the screen. But, I can not connect to my server by ssh client server from poor win98. (This is another problem >_<) So, I read FAQ. In FAQ said that I must check my ssh version, use command "ssh -V ". I did it, and then showed "segmentation fault" on my screen.. Why??? It is just simple command. Hope someone can tell me why. Please!! *_* And thanks for who read this mail.^^ haheho
Re: Segmentation Fault & All possible solutions Please.
[EMAIL PROTECTED] wrote: >Dear members, > Here is something I have not been really been able to understand .. SEGME >NTATION >FAULT . > Please tell m: >1)What exactly is segmentation fault ? >2)When does it occur ? >3)How Do you Solve it ? It means that a program has tried to address memory that does not belong to it. It is likely to occur if the program uses an uninitialised pointer. There can be many causes, all of which come down to programmer error. You solve it first by using the debugger to find the pointer which is at fault and second by carefully writing your programs so that they never try to access invalid pointers. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "For whosoever shall call upon the name of the Lord shall be saved." Romans 10:13
Segmentation Fault & All possible solutions Please.
Dear members, Here is something I have not been really been able to understand .. SEGMENTATION FAULT . Please tell m: 1)What exactly is segmentation fault ? 2)When does it occur ? 3)How Do you Solve it ? Please help
XF86Setup "segmentation fault"
I'm working on upgrading to woody, and here's my latest x windows problem: I'd installed xdm and xbase-clients (with all the dependent files and stuff) then i ran XF86Setup, which worked fine at this point. Afterwards, I finished my x installation by dpkg ing xserver-common, and xserver-svga (which i believe is the right sever for my TNT2 graphics card). I ran x, which started momentarily, but is of no use, because i accidentally forgot to hit "update" when configuring the mouse. So now i need to re-configure (preferably w/ XF86Setup b/c its so much quicker and easier and isn't something that i want to remain broken). I ran XF86Setup and errors similar to these streamed off the screen: "Warning Server spcification missing in card database entry for " or "Warning Chipset spcification missing in card database entry for " which ended with the ambiguous "segmentation fault" message. Since then i've tried to re-install XF86Setup (the potato version as that's the only on i can find on the debian packages page) but that wasn't be problem b/c i'm getting the same errors. What do i need to do? Install all\another xserver package perhaps? At this point, i'm open to suggestions from people that have the slightest idea waht they're talking a/b as i'm not getting much help with this problem. thanks a lot...hopefully i won't have to go back to potato if i get this working
Warnquota - Segmentation Fault
Hello, Can anyone help me? Every time I run "warnquota" the system returns the following error: Segmentation fault No recipient addresses found in header Until the last week or so, the warnquota tool had been working very well. Any information that could be used to correct this problem would be truly appreciated. Thank you Dave Bacon Computer Network Manager Outagamie Waupaca Library System 225 N. Oneida St. Appleton, WI 54911
Re: C programming: Segmentation fault within malloc?
Richard Cobbe writes: > heap. Unfortunately, this may or may not be the location of the root > error. While I'm a big fan of garbage collectors in general, I don't think You can always hope that it's a piece of memory you were dealing with before. Depending on the malloc debugger, you may also be able to see whose memory you're stepping on (if anybody's). > that using one here will help you find the cause of this crash. When you've > got a GC, you typically don't ever call free(), and a GC won't protect much > against the last two causes I mentioned above. As a result, it will most > likely hide the bug, or not affect it at all. Ah, but it does give you info, which helps. If the bug disappears, you know it's something only a GC could fix (unless the bug is non-reproducible)--okay, even then, it's still only a good probability since the GC will change memory access patterns. If it doesn't disappear, then you're doing something nastier with the memory. Again, probably, but all clues help with memory debugging. Andrew.
Re: C programming: Segmentation fault within malloc?
Lo, on Thursday, July 26, Shaul Karl did write: > Program received signal SIGSEGV, Segmentation fault. > 0x400af19e in malloc () from /lib/libc.so.6 > (gdb) > > > How can it be? If malloc can not allocate memory it should return a NULL > pointer. How can it Seg fault? As Andrew Agno and Alan Shutko point out elsewhere in this thread, this is most likely due to an inadvertent corruption of the language runtime's accounting data in the heap (the area of memory managed by malloc() and free()). Typical causes: * freeing the same pointer twice * freeing a stack or global variable * in general, calling free() with any argument that was not returned by malloc(). * walking off the end of an array on the heap and clobbering some accounting data. * chasing a bogus pointer and clobbering some accounting data Rick Macdonald suggested that the first malloc may be returning 0, and the second would therefore attempt to set node->data to some other pointer, in spite of the fact that node is null. This could conceivably be possible (although, as you say, C's short-circuit boolean evaluation means it won't happen), but it wouldn't produce the results that you're seeing. The implementation of malloc() doesn't know anything about what you're going to do with the result. If, therefore, you tried to assign the second malloc's result to node->data when node is in fact null, you'd get a seg fault after you returned from the second malloc, not during it. The actual cause of the crash is likely to be quite distant (either in time, or in space, or both) from the failing malloc(), so figuring out exactly which malloc() crashes isn't likely to do you much good. As Andrew suggested, using a memory debugging tool like Electric Fence or Debauch may help you find the point in your program at which you smash the heap. Unfortunately, this may or may not be the location of the root error. While I'm a big fan of garbage collectors in general, I don't think that using one here will help you find the cause of this crash. When you've got a GC, you typically don't ever call free(), and a GC won't protect much against the last two causes I mentioned above. As a result, it will most likely hide the bug, or not affect it at all. These tend to be fairly nasty bugs to find and fix. Best of luck! Richard
Re: C programming: Segmentation fault within malloc?
>
> Try breaking the mallocs into separate lines to see which one fails:
>
> int errflag = 0;
> if (!(node = (struct node *)malloc(sizeof(struct node {
> errflag = 1;
> } else {
> if (!(node->data = (struct symbol *)malloc(sizeof(struct
> symbol {
>errflag = 2;
> }
> }
> if (errflag) {
> fprintf(stderr, "errflag=%d\n");
> fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> return FALSE;
> }
>
> If the first one sets errflag without a segfault in malloc, it would seem
> that your original compound statement tried to do the second malloc. The
> second malloc would certainly fail if the first malloc results in "node"
> being a null pointer, because it would try to set node->data. You can try
> to test this with:
The C language guarantees that with such AND logical expression, the 2nd
operand will not be executed unless the first operand has a logical value of
TRUE.
The real problem was that I was convinced that realloc(void*, size_t) does not
free the previously allocated area; and therefore have free it myself. That
was done much earlier then when malloc segfault since the error manifested
itself only when malloc had to run again.
>
> if (!((node = (struct node *)malloc(sizeof(struct node))) &&
>(fprintf (stderr, "should not get here\n" {
> }
>
>
> On Thu, 26 Jul 2001, Shaul Karl wrote:
>
> > > Have you tried to look at the value sizeof(struct node)? It might be too
> > > big.
> > > Otherwise, can you show us the backtrace in gdb.
> > >
> >
> >
> > gdb says sizeof(struct node) == 20. It is mostly a couple of pointers:
> >
> > struct node {
> > enum colors color;
> > struct node *left, *right, *parent;
> > void *data;
> > };
> >
> >
> > Breakpoint 1, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> > 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > (gdb) p sizeof(struct node)
> > $1 = 20
> > (gdb) c
> > Continuing.
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x400af19e in malloc () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x400af19e in malloc () from /lib/libc.so.6
> > #1 0x400ae844 in malloc () from /lib/libc.so.6
> > #2 0x804c60a in insert_symbol (sym=0xbfffe25c) at symbols.c:197
> > #3 0x8048c6f in tmp_variable (tmp=0xbfffe398, sym_data=0xbfffe2ec)
> > at actions.c:115
> > #4 0x80497be in sym_for_const (tok=0xbfffe4f8, sym=0xbfffe398)
> > at actions.c:412
> > #5 0x804d55f in yyparse () at parser.y:216
> > #6 0x804ddd5 in translator (params=0xbb80) at parser.y:272
> > #7 0x804b08f in main (argc=1, argv=0xbc98) at main.c:195
> > #8 0x4005b2db in __libc_start_main () from /lib/libc.so.6
> > (gdb)
> >
> > I believe that malloc is called twice here due to line 198:
> >
> > if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > (node->data = malloc(sizeof(struct symbol) {
> >
> > and sizeof(struct symbol) is 52.
> >
> >
> >
> > > On [Thu, 26 Jul 2001 03:15:46 +0300], Shaul Karl <[EMAIL PROTECTED]>
> > > wrote:
> > > > Breakpoint 2, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> > > > 197 if (!((node = (struct node *)malloc(sizeof(struct node)))
> > > > &&
> > > > (gdb) l 197
> > > > 192
> > > > 193 enum flag insert_symbol(struct symbol *sym)
> > > > 194 {
> > > > 195 struct node *node;
> > > > 196
> > > > 197 if (!((node = (struct node *)malloc(sizeof(struct node)))
> > > > &&
> > > > 198 (node->data = (struct symbol *)malloc(sizeof(struct
> > > > symbol) {
> > > > 199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> > > > 200 return FALSE;
> > > > 201 }
> > > > (gdb) n
> > > >
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > 0x400af19e in malloc () from /lib/libc.so.6
> > > > (gdb)
> > > >
> > > >
> > > > How can it be? If malloc can not allocate memory it should return a
> > > > NULL
> > > > pointer. How can it Seg fault?
> > > >
> > > > [03:09:45 16]$ free
&g
Re: C programming: Segmentation fault within malloc?
Shaul Karl <[EMAIL PROTECTED]> writes: > How can it be? If malloc can not allocate memory it should return a NULL > pointer. How can it Seg fault? You have most likely overwritten the end of an array and overwritten malloc's accounting info, causing a segfault next time you malloc something. -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! "Every man has his price. Mine is $3.95."
Re: C programming: Segmentation fault within malloc?
> > > On Thu, 26 Jul 2001, Shaul Karl wrote: > > > How can it be? If malloc can not allocate memory it should return a NULL > > pointer. How can it Seg fault? > > The internal state of the stack became corrupted. Try compiling with > "-lefence" (electric fence). Then reproduce the error. It will crash > again, but with a bit of luck at the place where the actual error is. > > Walter > Thank you. With efence pin pointing the point of failure I have managed to learn that realloc(void*, size_t) frees the other size allocated memory. For some reason I was convinced that it does not. -- Shaul Karl <[EMAIL PROTECTED]>
Re: C programming: Segmentation fault within malloc?
* Shaul Karl ([EMAIL PROTECTED]) spake thusly:
...
> 193 enum flag insert_symbol(struct symbol *sym)
> 194 {
> 195 struct node *node;
> 196
> 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> 198 (node->data = (struct symbol *)malloc(sizeof(struct
> symbol) {
> 199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> 200 return FALSE;
> 201 }
> (gdb) n
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x400af19e in malloc () from /lib/libc.so.6
> (gdb)
You know, I tend to write simple stupid code these days. When the above
is written like
node = (struct node *)malloc(...);
if( node == NULL ) return( E_MALLOC );
tmp = (struct symbol *)malloc(...);
if( tmp == NULL ) return( E_MALLOC );
node->data = tmp;
it's easier to debug. Presumably the compiler will optimize this form and
your form to about the same sequence of instructions, so you don't gain
much by stringing it into single if statement. OTGH with simple stupid code
you can see which malloc() segfaults.
> How can it be? If malloc can not allocate memory it should return a NULL
> pointer. How can it Seg fault?
Well, I've seen gcc overwrite previously allocated memory and _not_ segfault,
so I wouldn't get too excited here.
Dima
--
E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home)
http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key
One distinguishing characteristic of BOFHen is attention deficit disorder.
Put me in front of something boring and I can find a near-infinite number
of really creative ways to bugger off. -- Antony De Boer in asr
Re: C programming: Segmentation fault within malloc?
Try breaking the mallocs into separate lines to see which one fails:
int errflag = 0;
if (!(node = (struct node *)malloc(sizeof(struct node {
errflag = 1;
} else {
if (!(node->data = (struct symbol *)malloc(sizeof(struct
symbol {
errflag = 2;
}
}
if (errflag) {
fprintf(stderr, "errflag=%d\n");
fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
return FALSE;
}
If the first one sets errflag without a segfault in malloc, it would seem
that your original compound statement tried to do the second malloc. The
second malloc would certainly fail if the first malloc results in "node"
being a null pointer, because it would try to set node->data. You can try
to test this with:
if (!((node = (struct node *)malloc(sizeof(struct node))) &&
(fprintf (stderr, "should not get here\n" {
}
On Thu, 26 Jul 2001, Shaul Karl wrote:
> > Have you tried to look at the value sizeof(struct node)? It might be too
> > big.
> > Otherwise, can you show us the backtrace in gdb.
> >
>
>
> gdb says sizeof(struct node) == 20. It is mostly a couple of pointers:
>
> struct node {
> enum colors color;
> struct node *left, *right, *parent;
> void *data;
> };
>
>
> Breakpoint 1, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> (gdb) p sizeof(struct node)
> $1 = 20
> (gdb) c
> Continuing.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x400af19e in malloc () from /lib/libc.so.6
> (gdb) bt
> #0 0x400af19e in malloc () from /lib/libc.so.6
> #1 0x400ae844 in malloc () from /lib/libc.so.6
> #2 0x804c60a in insert_symbol (sym=0xbfffe25c) at symbols.c:197
> #3 0x8048c6f in tmp_variable (tmp=0xbfffe398, sym_data=0xbfffe2ec)
> at actions.c:115
> #4 0x80497be in sym_for_const (tok=0xbfffe4f8, sym=0xbfffe398)
> at actions.c:412
> #5 0x804d55f in yyparse () at parser.y:216
> #6 0x804ddd5 in translator (params=0xbb80) at parser.y:272
> #7 0x804b08f in main (argc=1, argv=0xbc98) at main.c:195
> #8 0x4005b2db in __libc_start_main () from /lib/libc.so.6
> (gdb)
>
> I believe that malloc is called twice here due to line 198:
>
> if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> (node->data = malloc(sizeof(struct symbol) {
>
> and sizeof(struct symbol) is 52.
>
>
>
> > On [Thu, 26 Jul 2001 03:15:46 +0300], Shaul Karl <[EMAIL PROTECTED]> wrote:
> > > Breakpoint 2, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> > > 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > > (gdb) l 197
> > > 192
> > > 193 enum flag insert_symbol(struct symbol *sym)
> > > 194 {
> > > 195 struct node *node;
> > > 196
> > > 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > > 198 (node->data = (struct symbol *)malloc(sizeof(struct
> > > symbol) {
> > > 199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> > > 200 return FALSE;
> > > 201 }
> > > (gdb) n
> > >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > 0x400af19e in malloc () from /lib/libc.so.6
> > > (gdb)
> > >
> > >
> > > How can it be? If malloc can not allocate memory it should return a NULL
> > > pointer. How can it Seg fault?
> > >
> > > [03:09:45 16]$ free
> > > total used free sharedbuffers cached
> > > Mem: 63584 60936 2648 31452 1344 20472
> > > -/+ buffers/cache: 39120 24464
> > > Swap: 116924 52580 64344
> > > [03:09:49 16]$
> > >
> > > Since all the memory is used and the machine is running for some time
> > > now,
> > > doesn't that precludes hardware problems?
> > >
> > > Obviously I am missing something.
> > >
> > >
> > > --
> > >
> > > Shaul Karl <[EMAIL PROTECTED]>
> > >
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > >
> >
> > --
> > Shao Zhang Tel: (02) 9209 4838
> > Software Engineer Fax: (02) 9209 4992
> > Redfern Broadband Networks (RBN)Mail: [EMAIL PROTECTED]
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
>
> --
>
> Shaul Karl <[EMAIL PROTECTED]>
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
...RickM...
Re: C programming: Segmentation fault within malloc?
> Have you tried to look at the value sizeof(struct node)? It might be too big.
> Otherwise, can you show us the backtrace in gdb.
>
gdb says sizeof(struct node) == 20. It is mostly a couple of pointers:
struct node {
enum colors color;
struct node *left, *right, *parent;
void *data;
};
Breakpoint 1, insert_symbol (sym=0xbfffe25c) at symbols.c:197
197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
(gdb) p sizeof(struct node)
$1 = 20
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x400af19e in malloc () from /lib/libc.so.6
(gdb) bt
#0 0x400af19e in malloc () from /lib/libc.so.6
#1 0x400ae844 in malloc () from /lib/libc.so.6
#2 0x804c60a in insert_symbol (sym=0xbfffe25c) at symbols.c:197
#3 0x8048c6f in tmp_variable (tmp=0xbfffe398, sym_data=0xbfffe2ec)
at actions.c:115
#4 0x80497be in sym_for_const (tok=0xbfffe4f8, sym=0xbfffe398)
at actions.c:412
#5 0x804d55f in yyparse () at parser.y:216
#6 0x804ddd5 in translator (params=0xbb80) at parser.y:272
#7 0x804b08f in main (argc=1, argv=0xbc98) at main.c:195
#8 0x4005b2db in __libc_start_main () from /lib/libc.so.6
(gdb)
I believe that malloc is called twice here due to line 198:
if (!((node = (struct node *)malloc(sizeof(struct node))) &&
(node->data = malloc(sizeof(struct symbol) {
and sizeof(struct symbol) is 52.
> On [Thu, 26 Jul 2001 03:15:46 +0300], Shaul Karl <[EMAIL PROTECTED]> wrote:
> > Breakpoint 2, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> > 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > (gdb) l 197
> > 192
> > 193 enum flag insert_symbol(struct symbol *sym)
> > 194 {
> > 195 struct node *node;
> > 196
> > 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> > 198 (node->data = (struct symbol *)malloc(sizeof(struct
> > symbol) {
> > 199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> > 200 return FALSE;
> > 201 }
> > (gdb) n
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x400af19e in malloc () from /lib/libc.so.6
> > (gdb)
> >
> >
> > How can it be? If malloc can not allocate memory it should return a NULL
> > pointer. How can it Seg fault?
> >
> > [03:09:45 16]$ free
> > total used free sharedbuffers cached
> > Mem: 63584 60936 2648 31452 1344 20472
> > -/+ buffers/cache: 39120 24464
> > Swap: 116924 52580 64344
> > [03:09:49 16]$
> >
> > Since all the memory is used and the machine is running for some time now,
> > doesn't that precludes hardware problems?
> >
> > Obviously I am missing something.
> >
> >
> > --
> >
> > Shaul Karl <[EMAIL PROTECTED]>
> >
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
>
> --
> Shao Zhang Tel: (02) 9209 4838
> Software Engineer Fax: (02) 9209 4992
> Redfern Broadband Networks (RBN)Mail: [EMAIL PROTECTED]
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Shaul Karl <[EMAIL PROTECTED]>
Re: C programming: Segmentation fault within malloc?
Have you tried to look at the value sizeof(struct node)? It might be too big.
Otherwise, can you show us the backtrace in gdb.
On [Thu, 26 Jul 2001 03:15:46 +0300], Shaul Karl <[EMAIL PROTECTED]> wrote:
> Breakpoint 2, insert_symbol (sym=0xbfffe25c) at symbols.c:197
> 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> (gdb) l 197
> 192
> 193 enum flag insert_symbol(struct symbol *sym)
> 194 {
> 195 struct node *node;
> 196
> 197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
> 198 (node->data = (struct symbol *)malloc(sizeof(struct
> symbol) {
> 199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
> 200 return FALSE;
> 201 }
> (gdb) n
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x400af19e in malloc () from /lib/libc.so.6
> (gdb)
>
>
> How can it be? If malloc can not allocate memory it should return a NULL
> pointer. How can it Seg fault?
>
> [03:09:45 16]$ free
> total used free sharedbuffers cached
> Mem: 63584 60936 2648 31452 1344 20472
> -/+ buffers/cache: 39120 24464
> Swap: 116924 52580 64344
> [03:09:49 16]$
>
> Since all the memory is used and the machine is running for some time now,
> doesn't that precludes hardware problems?
>
> Obviously I am missing something.
>
>
> --
>
> Shaul Karl <[EMAIL PROTECTED]>
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Shao Zhang Tel: (02) 9209 4838
Software Engineer Fax: (02) 9209 4992
Redfern Broadband Networks (RBN)Mail: [EMAIL PROTECTED]
RE:C programming: Segmentation fault within malloc?
Shaul Karl writes: > Obviously I am missing something. Since it's fairly unlikely that malloc is wrong, then you've got something like memory being freed twice, or accessing freed memory or something along those lines. It only happens to show up when you do the malloc. A quick check would be to use a garbage collector for C: http://www.hpl.hp.com/personal/Hans_Boehm/gc/ or Electric Fence: http://www.perens.com/FreeSoftware/ or Debauch: http://quorum.tamu.edu/jon/gnu/ Debauch and Electric Fence are in Debian testing, too. Andrew.
C programming: Segmentation fault within malloc?
Breakpoint 2, insert_symbol (sym=0xbfffe25c) at symbols.c:197
197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
(gdb) l 197
192
193 enum flag insert_symbol(struct symbol *sym)
194 {
195 struct node *node;
196
197 if (!((node = (struct node *)malloc(sizeof(struct node))) &&
198 (node->data = (struct symbol *)malloc(sizeof(struct
symbol) {
199 fprintf(stderr, sym_tab_msg[MEMORY_ALLOCATION_FAILURE]);
200 return FALSE;
201 }
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0x400af19e in malloc () from /lib/libc.so.6
(gdb)
How can it be? If malloc can not allocate memory it should return a NULL
pointer. How can it Seg fault?
[03:09:45 16]$ free
total used free sharedbuffers cached
Mem: 63584 60936 2648 31452 1344 20472
-/+ buffers/cache: 39120 24464
Swap: 116924 52580 64344
[03:09:49 16]$
Since all the memory is used and the machine is running for some time now,
doesn't that precludes hardware problems?
Obviously I am missing something.
--
Shaul Karl <[EMAIL PROTECTED]>
Re: licq segmentation fault
On Tue, 5 Jun 2001, Blue Rat wrote: > The subject sums it up, basically. LICQ crashes as soon as it starts. Hmm, > I wonder whether Everybuddy has multilanguage support... or Gnome-ICU... > > Ah well, what the hell. Comments, suggestions? > What version of licq? I had dramas at one stage, but everything is fine with version 1.0.3 cheers dc Today people in droves hurry up past Heumoz to Villars on the road to the ski hills, so they can rush down them as fast as possible, so they can hurry up again in order to rush down again. In a way this is funny,... Francis A Schaeffer David Purton http://www.chariot.net.au/~dcpurton/ [EMAIL PROTECTED]
licq segmentation fault
The subject sums it up, basically. LICQ crashes as soon as it starts. Hmm, I wonder whether Everybuddy has multilanguage support... or Gnome-ICU... Ah well, what the hell. Comments, suggestions? Cheerio, Pope Mickey XXIII, finally enjoying sound under Debian. PS To those interested (I've had that wee bit of trouble with resolving hosts), everything started working automagickally. Go figure. -- " ...and this is the place where she cut her wrists that odd and fateful night And I say "Oh oh oh oh oh Oh oh - what a feeling". --Lou Reed
Re: licq segmentation fault
Blue Rat wrote on Tue Jun 05, 2001 at 03:45:55PM: > The subject sums it up, basically. LICQ crashes as soon as it starts. Which licq version? What exactely means "crashes"? does it segfault? Are all necessary libraries installed / found (man ldd)? Any (error) messages from licq (start it from an xterm)? login into existing account or new account? Also see http://www.licq.org/faq.html> Matthias -- Matthias Richter --+- stud. soz. & inf. -+-- http://www.uni-leipzig.de -->GPG Public Key: http://www.matthias-richter.de/gpg.ascii<-- pgpAdozwU33Im.pgp Description: PGP signature
Re: licq segmentation fault
I have an issue too with LICQ only with Debian unstable Whether I use apt-get to install, or I compile my own from either the stable tarball or from the cvs, whenever I start a message, then change the message to another kind, like for example, to a file transfer request instead, LICQ will quit and the following is observer: Licq Segmentation Violation Detected. Backtrace: licq(licq_handle_sigsegv+0x73) [0x80924db] /lib/libpthread.so.0(pthread_kill+0x170) [0x40121dd4] /lib/libc.so.6(__libc_sigaction+0x1f8) [0x401c2a28] /usr/lib/libqt.so.2(notify__12QApplicationP7QObjectP6QEvent+0x1d2) [0x404e27ae] /usr/lib/libqt.so.2(eventFilter__9QComboBoxP7QObjectP6QEvent+0xbc4) [0x405a0e8c] /usr/lib/libqt.so.2(activate_filters__7QObjectP6QEvent+0x74) [0x405345b0] /usr/lib/libqt.so.2(event__7QWidgetP6QEvent+0x2b) [0x4057d4af] /usr/lib/libqt.so.2(notify__12QApplicationP7QObjectP6QEvent+0x1d2) [0x404e27ae] /usr/lib/libqt.so.2(translateMouseEvent__9QETWidgetPC7_XEvent+0x8d6) [0x404b0ff6] /usr/lib/libqt.so.2(x11ProcessEvent__12QApplicationP7_XEvent+0x7c3) [0x404aec7f] /usr/lib/libqt.so.2(processNextEvent__12QApplicationb+0x70) [0x404adc4c] /usr/lib/libqt.so.2(enter_loop__12QApplication+0x43) [0x404e4bef] /usr/lib/libqt.so.2(exec__12QApplication+0x2b) [0x404b5193] /usr/local/lib/licq/licq_qt-gui.so(Run__8CLicqGuiP10CICQDaemon+0xf9) [0x402f8341] /usr/local/lib/licq/licq_qt-gui.so(LP_Main+0x28) [0x402f6778] /usr/local/lib/licq/licq_qt-gui.so(LP_Main_tep+0x21) [0x402f64a1] /lib/libpthread.so.0(pthread_detach+0x519) [0x4011efc5] /lib/libc.so.6(__clone+0x3a) [0x40261c2a] Attempting to generate core file. -- Eric Boo Wednesday, June 06, 2001, 12:08 PM 40 hours and 47 minutes http://magicman.freeshell.org
Re: licq segmentation fault
i solved that buy changing my kde2 plugin (wich i never ment 2 install) back to the qt2 plugin and that's all!! hope it helps! * Eric Boo ([EMAIL PROTECTED]) wrote: > I have an issue too with LICQ only with Debian unstable > > Whether I use apt-get to install, or I compile my own from either the stable > tarball or from the cvs, whenever I start a message, then change the message > to another kind, like for example, to a file transfer request instead, LICQ > will quit and the following is observer: > > > Licq Segmentation Violation Detected. > Backtrace: > licq(licq_handle_sigsegv+0x73) [0x80924db] > /lib/libpthread.so.0(pthread_kill+0x170) [0x40121dd4] > /lib/libc.so.6(__libc_sigaction+0x1f8) [0x401c2a28] > /usr/lib/libqt.so.2(notify__12QApplicationP7QObjectP6QEvent+0x1d2) > [0x404e27ae] > /usr/lib/libqt.so.2(eventFilter__9QComboBoxP7QObjectP6QEvent+0xbc4) > [0x405a0e8c] > /usr/lib/libqt.so.2(activate_filters__7QObjectP6QEvent+0x74) [0x405345b0] > /usr/lib/libqt.so.2(event__7QWidgetP6QEvent+0x2b) [0x4057d4af] > /usr/lib/libqt.so.2(notify__12QApplicationP7QObjectP6QEvent+0x1d2) > [0x404e27ae] > /usr/lib/libqt.so.2(translateMouseEvent__9QETWidgetPC7_XEvent+0x8d6) > [0x404b0ff6] > /usr/lib/libqt.so.2(x11ProcessEvent__12QApplicationP7_XEvent+0x7c3) > [0x404aec7f] > /usr/lib/libqt.so.2(processNextEvent__12QApplicationb+0x70) [0x404adc4c] > /usr/lib/libqt.so.2(enter_loop__12QApplication+0x43) [0x404e4bef] > /usr/lib/libqt.so.2(exec__12QApplication+0x2b) [0x404b5193] > /usr/local/lib/licq/licq_qt-gui.so(Run__8CLicqGuiP10CICQDaemon+0xf9) > [0x402f8341] > /usr/local/lib/licq/licq_qt-gui.so(LP_Main+0x28) [0x402f6778] > /usr/local/lib/licq/licq_qt-gui.so(LP_Main_tep+0x21) [0x402f64a1] > /lib/libpthread.so.0(pthread_detach+0x519) [0x4011efc5] > /lib/libc.so.6(__clone+0x3a) [0x40261c2a] > Attempting to generate core file. > > -- > Eric Boo > Wednesday, June 06, 2001, 12:08 PM > 40 hours and 47 minutes > > http://magicman.freeshell.org > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: licq segmentation fault
Verily, on 06 Jun 2001 11:52AM (-0300), Sergio E. Schvezov thusly proclaimed: -> i solved that buy changing my kde2 plugin (wich i never ment 2 install) -> back to the qt2 plugin and that's all!! -> -> hope it helps! Hi, I didn't install any KDE2 plugins. In fact, when configuring the qt plugin, it says that KDE2 is disabled. Thanks for your help anyway.
Warnquota - Segmentation fault
Hello, Can anyone help me? Every time I run "warnquota" the system returns the following error: Segmentation fault No recipient addresses found in header Any information that could be used to correct this problem would be truly appreciated. Thank you -- _ Dave G. Bacon Computer Network Manager Outagamie Waupaca Library System 225 N. Oneida St., Appleton, WI 54911 920/832-6193(voice), 920/832-6422(FAX) mailto:[EMAIL PROTECTED] http://www.owls.lib.wi.us _
Re: Segmentation fault
Okay, after I closed gimp and run apt-get install gphoto again, the installation succeeded. Thanks for your attention. Regards, --Wen [EMAIL PROTECTED] wen> When I try to install gphoto by apt-get from unstable, I got the following wen> error message and finally the installation failed. Could someone help me?
Segmentation fault
Hi, When I try to install gphoto by apt-get from unstable, I got the following error message and finally the installation failed. Could someone help me? Regards, --Wen [EMAIL PROTECTED] # apt-get install gphoto Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: imagemagick libbz2-1.0 libc6 libc6-dev libdb2 libdb2-util libdps1 libfreetype6 libhdf4g libmagick5 libncurses5 libnetpbm9 libwmf0 libxml2 netpbm The following NEW packages will be installed: gphoto imagemagick libbz2-1.0 libdps1 libfreetype6 libhdf4g libmagick5 libnetpbm9 libwmf0 libxml2 netpbm 5 packages upgraded, 11 newly installed, 0 to remove and 232 not upgraded. Need to get 11.3MB of archives. After unpacking 16.8MB will be used. Do you want to continue? [Y/n] Get:1 ftp://ftp.jp.debian.org unstable/main libmagick5 1:5.3.0-4 [1293kB] Get:2 ftp://ftp.jp.debian.org unstable/main libdb2 2:2.7.7-4 [272kB] Get:3 ftp://ftp.jp.debian.org unstable/main libc6 2.2.2-4 [3171kB] Get:4 ftp://ftp.jp.debian.org unstable/main libncurses5 5.2.20010318-1 [226kB] Get:5 ftp://ftp.jp.debian.org unstable/main libc6-dev 2.2.2-4 [2240kB] Get:6 ftp://ftp.jp.debian.org unstable/main gphoto 0.4.3-2 [725kB] Get:7 ftp://ftp.jp.debian.org unstable/main imagemagick 1:5.3.0-4 [1214kB] Get:8 ftp://ftp.jp.debian.org unstable/main libbz2-1.0 1.0.1-6 [32.7kB] Get:9 ftp://ftp.jp.debian.org unstable/main libdb2-util 2:2.7.7-4 [107kB] Get:10 ftp://ftp.jp.debian.org unstable/main libdps1 4.0.2-12 [172kB] Get:11 ftp://ftp.jp.debian.org unstable/main libfreetype6 2.0.1.20010317-1 [170kB] Get:12 ftp://ftp.jp.debian.org unstable/main libhdf4g 4.1r4-4 [240kB] Get:13 ftp://ftp.jp.debian.org unstable/main libnetpbm9 2:9.10-3 [56.2kB] Get:14 ftp://ftp.jp.debian.org unstable/main libwmf0 0.1.21-1 [126kB] Get:15 ftp://ftp.jp.debian.org unstable/main libxml2 2.3.5-1 [224kB] Get:16 ftp://ftp.jp.debian.org unstable/main netpbm 2:9.10-3 [1037kB] Fetched 11.3MB in 25m23s (7421B/s) dpkg: error processing /var/cache/apt/archives/libdb2-util_2%3a2.7.7-4_i386.deb (--unpack): subprocess dpkg-split killed by signal (Segmentation fault) dpkg: error processing /var/cache/apt/archives/libdb2_2%3a2.7.7-4_i386.deb (--unpack): subprocess dpkg-split killed by signal (Segmentation fault) dpkg: error processing /var/cache/apt/archives/libc6-dev_2.2.2-4_i386.deb (--unpack): subprocess dpkg-split killed by signal (Segmentation fault) dpkg: error processing /var/cache/apt/archives/libc6_2.2.2-4_i386.deb (--unpack): subprocess dpkg-split killed by signal (Segmentation fault) E: Sub-process /usr/bin/dpkg exited unexpectedly
gmc segmentation fault
hello, I have solved my problem with debconf but gmc always dislays the message "segmentation fault" and the address for help does not exist on the WEB. Can someone advise me, please, how to deal with this problem. I can't use gdb gmc core because gmc had not been compiled with the option -g. THanks for your help. -- Gerard
Re: [menuconfig] Segmentation fault
Just a final note on the problem that I was having. I tried recompiling the kernel yet another time and finally it worked. I suppose the problem with the memory still persists, but it didn't rear it's head on this occasion. Strange!!! Or maybe not. Anyway, thanks again. T:Irvine
Re: [menuconfig] Segmentation fault
>to test copy the /boot/config-2.2.17 file to >/usr/src/linux/.config (or wherever you put the kernel >source) and run > >make dep ; make clean ; make bzImage I tried a slight variation on this idea. I ran menuconfig again, made a few changes and saved the configuration file before it had time to crash. I then ran /usr/bin/make-kpkg clean...went O.K and then /usr/bin/make-kpkg --revision=custom.1.0 kernel-image \ 2>&1 | tee ~/kernel-compile.txt and it crashed again. From the file ~/kernel-compile.txt it was clear that there was a 'fatal signal 11' which I understand means that there is some problem with the memory. I suppose that that was the problem all along. Thanks for your assistance. I suppose I'll need some new memory for this computer or maybe I'll try and remove some of it's memory and try to find out which one of the memory modules is at fault. Thanx again. T:Irvine
Re: [menuconfig] Segmentation fault
irvine wrote: > > Hello!!! > > I recently bought and installed Debian 2.2r0. > I installed it and decided to compile a new > kernel. > > PROBLEM: > > I used 'menuconfig' but after a while > it exits suddenly. The message > > 'make: *** [menuconfig] Segmentation fault' > > is appears and the command prompt returns. > > I was trying to use kernel-source-2.2.17 > which I had installed from the cd-rom using > dselect. > > Has anyone any ideas that can help me find out > what may have gone wrong. hmm, just to test copy the /boot/config-2.2.17 file to /usr/src/linux/.config (or wherever you put the kernel source) and run make dep ; make clean ; make bzImage and repeat that a few times ..see if it segfaults again ive never had menuconfig segfault on a stable kernel maybe something else is at work here ..can't imagine what it is though. does it crash at the same point? also what is your terminal emulation? are you on the console or are you doing this through some sort of telnet/ssh or xterm or something nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
[menuconfig] Segmentation fault
Hello!!! I recently bought and installed Debian 2.2r0. I installed it and decided to compile a new kernel. PROBLEM: I used 'menuconfig' but after a while it exits suddenly. The message 'make: *** [menuconfig] Segmentation fault' is appears and the command prompt returns. I was trying to use kernel-source-2.2.17 which I had installed from the cd-rom using dselect. Has anyone any ideas that can help me find out what may have gone wrong. T:Irvine
Re: CD burning & mkisofs segmentation fault.
On Nov 27 2000, Daniel Ferrante wrote: > When I try to create an image (of, say, my home directory) after a > certain time, mkisofs reports a seg fault. The interesting thing is > that, this "certain time" varies every time I run the command! This is the most common case of a segmentation fault happening due to memory programs. Since mkisofs makes extensive use of memory in a short period of time, it actually happens to trigger bad memory quite easily. So, I'd recommend you to check your memory (use memtest86 -- use google for that) for 1 or 2 days. The fact that it happens randomly each time and that it freezes your system (does Linux issue an Oops?) seems to be a stronger evidence in that direction. []s, Roger... P.S.: Reply to the list. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: CD burning & mkisofs segmentation fault.
On Mon, 27 Nov 2000, Brian McGroarty wrote: > > I have been having some trouble with the mkisofs of the > > Debian/GNU Linux 2.2r0 (potato). When I try to create an image (of, say, > > my home directory) after a certain time, mkisofs reports a seg fault. The > > interesting thing is that, this "certain time" varies every time I run the > > command! Xcdroast does the same: after a while it bummers me with a > > message saying that "something went wrong"... Again, the "while" varies > > everytime. On top of this, every now and then, my system just freezes!!! > > I believe I followed all the steps in the CD-Writing howto and I > > have been through the documentation already... Any hints?! > > > > P.S.: Please, respond to [EMAIL PROTECTED], once I am not > > presently subscribing to this email list. Thanks again. > > Have you enough free space on your hard drive? mkisofs shouldn't be > using anything unusual, save a lot of drive space and a large amount > of disk i/o. > Yeap! I have about 4.0Gb of FREE space!!! That's why it's intriguing... ;) On top of that, I have about 128Mb of swap and 128Mb of RAM... My HD's are SCSI and my burner is ATAPI, but, other than that, I cannot think of anything else that could possibly be affecting... Daniel. __ Daniel Doro Ferrante email: [EMAIL PROTECTED] http://www.physics.brown.edu/Users/students/ferrante/index.html Physics Graduate Student - Brown University Course of Molecular Sciences - USP: http://www.cecm.usp.br
Re: CD burning & mkisofs segmentation fault.
> I have been having some trouble with the mkisofs of the > Debian/GNU Linux 2.2r0 (potato). When I try to create an image (of, say, > my home directory) after a certain time, mkisofs reports a seg fault. The > interesting thing is that, this "certain time" varies every time I run the > command! Xcdroast does the same: after a while it bummers me with a > message saying that "something went wrong"... Again, the "while" varies > everytime. On top of this, every now and then, my system just freezes!!! > > I believe I followed all the steps in the CD-Writing howto and I > have been through the documentation already... Any hints?! > >Daniel. > > P.S.: Please, respond to [EMAIL PROTECTED], once I am not > presently subscribing to this email list. Thanks again. Have you enough free space on your hard drive? mkisofs shouldn't be using anything unusual, save a lot of drive space and a large amount of disk i/o.
CD burning & mkisofs segmentation fault.
Hi Folks, I have been having some trouble with the mkisofs of the Debian/GNU Linux 2.2r0 (potato). When I try to create an image (of, say, my home directory) after a certain time, mkisofs reports a seg fault. The interesting thing is that, this "certain time" varies every time I run the command! Xcdroast does the same: after a while it bummers me with a message saying that "something went wrong"... Again, the "while" varies everytime. On top of this, every now and then, my system just freezes!!! I believe I followed all the steps in the CD-Writing howto and I have been through the documentation already... Any hints?! Daniel. P.S.: Please, respond to [EMAIL PROTECTED], once I am not presently subscribing to this email list. Thanks again. __ Daniel Doro Ferrante email: [EMAIL PROTECTED] http://www.physics.brown.edu/Users/students/ferrante/index.html Physics Graduate Student - Brown University Course of Molecular Sciences - USP: http://www.cecm.usp.br
Re: Segmentation Fault?
On Mon, Apr 17, 2000 at 12:11:50AM +0200, Oswald Buddenhagen wrote: > > using 2.1r5 (stable). > > first item installed after base is XFree86 3.3.6 glibc21 version. > > > i'm not sure, but isn't slink glibc 2.0? Yes, it is. If the original poster has his information right, that's probably the problem. -- finger for GPG public key. <>
Re: Copying / partition, segmentation fault
Brian Dockter wrote: > I've always used cpio for copying/moving entire file systems (although I > haven't yet > needed to on Debian yet). A command such as: > > find / -xdev -depth -print | cpio -pdm /mnt > > should also do the trick. I just hate replying to my own messages, but I caught a bug (although too late for inclusion in the original email) and decided I'd better fix it. The following commands should work better: cd / find . -xdev -depth -print | cpio -pdm /mnt I guess I need to do a better job of controlling my enthusiasm. :-) Brian -- Brian Dockter| Email: [EMAIL PROTECTED] Sr. Member Technical Staff | Voice: 425-771-2400 Sony Electronics, Seattle| FAX: 425-771-2066
Re: Copying / partition, segmentation fault
Brent Buchholz wrote: > On Wed, Oct 18, 2000 at 05:07:56PM +, Marvin Stodolsky wrote: > > The /dev/hda1 files were copied over with: > > cp -xa * /mnt with /dev/hdd2 on /mnt >^ > Two things I don't like about that: globbing and cp itself. I moved / with a > tar pipe. > > "cd /mnt" > "tar lO / | tar cvvf -" > > > Any suggestions as to potential causal factors? > > > Mabey cp wasn't able to preserve permissions? I've always used cpio for copying/moving entire file systems (although I haven't yet needed to on Debian yet). A command such as: find / -xdev -depth -print | cpio -pdm /mnt should also do the trick. Brian -- Brian Dockter| Email: [EMAIL PROTECTED] Sr. Member Technical Staff | Voice: 425-771-2400 Sony Electronics, Seattle| FAX: 425-771-2066
Re: Copying / partition, segmentation fault
On Wed, Oct 18, 2000 at 05:07:56PM +, Marvin Stodolsky wrote: > The /dev/hda1 files were copied over with: > cp -xa * /mnt with /dev/hdd2 on /mnt ^ Two things I don't like about that: globbing and cp itself. I moved / with a tar pipe. "cd /mnt" "tar lO / | tar cvvf -" > Any suggestions as to potential causal factors? > Mabey cp wasn't able to preserve permissions? Brent
Copying / partition, segmentation fault
A 54 Gig drive has been installed and Winswish & Linux paritions made, in preparing for a complete shift to the new disk. This is a udma66 Western Digital, but being driven off the old controller on an ASUS mother board, with a BIOS upgrade supporting the big disk. The new Linux root partition is a primary /dev/hdd2, physically at the back of the drive. The old installation on /dev/hda, with the well functioning Corel Linux has / partition /dev/hda1 and a /usr partition /dev/hda9. The /dev/hda1 files were copied over with: cp -xa * /mnt with /dev/hdd2 on /mnt The /etc/fstab and /etc/lilo.conf files were addressed to /dev/hdd2 During the bootup of /dev/hdd2 using LOADLIN, the old /dev/hda9 is mounted on /usr There have been a Segmentation Faults, per text below, and the system drops into runlevel 1 maintenance mode. Any suggestions as to potential causal factors? Please also respond to [EMAIL PROTECTED] . MarvS = Starting system log daemon: syslogd klogd. /etc/init.d/rc: /etc/rc2.d/S11pcmcia.txt: Permission denied Starting automounter: /mnt/amnt. /etc/rc2.d/S20exim: line 46: 311 Segmentation fault update-inetd --disable smtp Starting mouse interface server: gpm. Starting internet superserver: inetd. Starting printer spooler: 2000-10-18-09:05:09.545 Get_local_host: hostname 'stodolsk' bad lprng. Starting X font server: xfs/etc/rc2.d/S20xfs: line 88: 335 Segmentation fault start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON already running. Starting X TrueType Font Server: xfstt/etc/rc2.d/S20xfstt: line 51: 337 Segmentation fault start-stop-daemon --start --quiet --exec $XFSTT -- $ARGS . /etc/rc2.d/S80devicesupdate.sh: line 2: 339 Segmentation fault /usr/X11R6/bin/devicesupdate Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. Starting kde display manager: kdm/etc/rc2.d/S99kdm: line 39: 347 Segmentation fault start-stop-daemon --start --quiet --exec /usr/bin/X11/kdm . /etc/init.d/rc: /etc/rc2.d/S99kdm.txt: Permission denied
mailman segmentation fault
Hello,
I can't seem to load the administration page of my mailing
list any more.
I always get "Internal Server Error" and "Premature end of script
headers: /usr/lib/mailman/cgi-bin/admin" from apache. I haven't been
able to find any errors from mailman.
Other mailing lists work fine.
strace (from root) says (assuming I didn't mess anything up trying to
run strace on the CGI-script, I don't think so though):
open("/var/lib/mailman/lists/jokes/config.db", O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0660, st_size=167257, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x401b5000
read(5, "{s\23\0\0\0member_posting_onlyi\0\0\0\0s\35"..., 4096) = 4096
old_mmap(NULL, 167936, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x401f4000
read(5, "[...deleted...]"..., 159744) = 159744
read(5, "[...deleted...]"..., 4096) = 3417
brk(0x8167000) = 0x8167000
close(5) = 0
munmap(0x401b5000, 4096)= 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
It leaves the lock file lying around too, which really messes up subsequent
tests. I have to delete it manually.
snoopy# /usr/sbin/check_db jokes
/var/lib/mailman/lists/jokes/config.db is fine
/var/lib/mailman/lists/jokes/config.db.last is fine
I am really not sure what else I should do. How should I go about
confirming a post, ie letting it through?
Arrgghhh!
My computer is fully potato, and was up-to-date yesterday.
Thanks in advance.
--
Brian May <[EMAIL PROTECTED]>
Re: Segmentation fault
Johann Spies wrote: > > On Tue, Jul 04, 2000 at 11:12:00AM -0700, Eric G . Miller wrote: > > > Debian 2.1 doesn't use glibc 2.1.2. Think it uses 2.0.7 and there are > > some incompatibilities. You'll either need to recompile the program for > > Debian 2.1 systems, or upgrade them to potato. Probably easier to > > recompile if you have the source. But, then again, the sources might > > require glibc2.1. > > I think this is the reason why I constantly get a segmentation fault > when trying to run Wordperfect 8 on Potato. Is there a way to run > programs that needs glibc 2.0.7 on Potato like the "oldlibs" on slink? glibc 2.1.x is supposed to be binary compatible with executables that have been compiled with glibc 2.0.7. There are exceptions though - Star Office was a good example at the time that RedHat released their first glibc 2.1.x based distro (6.0). My recollection is that the version of Star Office at the time exploited a 'feature' (bug) of glibc 2.0.7, which was fixed in glibc 2.1 (hence it broke). Most stuff works okay though. I upgraded a RH5.2 box (glibc 2.0.7) to use glibc 2.1.3 just by installing the glibc rpm from RH6.2 over the top. The automounter was the only thing I noticed that broke (and I fixed that pretty easily). I didn't have to recompile or reinstall any other packages - the ones compiled with glibc 2.0.7 just work. Wordperfect might one of the programs that can't handle glibc 2.0.7 thought. I would think that Corel would have made an updated version available if that was the case. Matthew
Re: Segmentation fault
On Tue, Jul 04, 2000 at 11:12:00AM -0700, Eric G . Miller wrote: > Debian 2.1 doesn't use glibc 2.1.2. Think it uses 2.0.7 and there are > some incompatibilities. You'll either need to recompile the program for > Debian 2.1 systems, or upgrade them to potato. Probably easier to > recompile if you have the source. But, then again, the sources might > require glibc2.1. I think this is the reason why I constantly get a segmentation fault when trying to run Wordperfect 8 on Potato. Is there a way to run programs that needs glibc 2.0.7 on Potato like the "oldlibs" on slink? Johann -- J.H. Spies, Hugenotestraat 29, Posbus 80, Franschhoek, 7690, South Africa Tel/Faks 021-876-2337 Sel/Cell 082 898 1528(Johann) 082 255 2388(Hester) "God is our refuge and strength, a very present help in trouble." Psalms 46:1
Re: Segmentation fault
On Tue, Jul 04, 2000 at 02:17:15PM +, [EMAIL PROTECTED] wrote:
> I have a set of applications which have been ported to Linux. The
> code was compiled and linked on a SuSe system running glibc 2.1.2.
> This was found to run on earlier SuSe installations and also on Red
> Hat.
>
> When an attempt was made to run the aplications on a Debian 2.1
> installation the programs crashed whth a segmentation fault. I have
> looked at the libc.so.6 on this system and it is much smaller than
> that on the SuSe system.
>
> Can anyone explain the difference on the Debian system and how I
> could possibly overcome this ?
Debian 2.1 doesn't use glibc 2.1.2. Think it uses 2.0.7 and there are
some incompatibilities. You'll either need to recompile the program for
Debian 2.1 systems, or upgrade them to potato. Probably easier to
recompile if you have the source. But, then again, the sources might
require glibc2.1.
You can check library dependencies for an executable with ldd.
--
#! /bin/sh
echo 'Linux Must Die!' | wall
dd if=/dev/zero of=/vmlinuz bs=1 \
count=`du -Lb /vmlinuz | awk '{ /^([0-9])+/ ; print $1 }'`
shutdown -r now
Everywhere "Segmentation fault" I see .
Hi group! I have Debian 2.1r2 (Slink), recently I have installed linuxconf and XFree 3.3.3.6. In two cases I have the same problem. When I`m starting linuxconf or xfree86, XF86Setup or the other file from XFree 3.3.3.6 package it writes: "Segmentation fault" . P.S The same problem I have with XFree 4.0 . Big thanks, G0DModE [EMAIL PROTECTED] `<;)-|--<[8
Segmentation fault & X
I apologise in advance for the long message.
I seem to have screwed up xserver (not that it was operating that
well).
I used the Debian packages to set it up, but had trouble getting it to
recognise my "card" and monitor. The best I could get was a purported
640 x 480 screen, except that the message announcing success was (I'm
guessing) four times the size it should have been, the buttons for
selecting xvidtune, etc. were off the screen to the right (as was half
the message). I guessed at where the xvidtune button was, so I could
retune, but it saved the configuration. I could not get xvidtune to
run after that.
I downloaded XF86 3.3.6, and tried to install, but could not get
extract to work, so simply gzip'd and tar'd the files into place.
Clearly a mistake. Attempts to run startx, xf86config, or XF86Setup
now end in error messages.
What is my best course of action, please? It appears to be necessary
to generate two or three scripts or files, but I don't know about the
segmentation fault.
I am very new to Linux, so could be missing something very obvious to
those more experienced.
I have run strace on all three of the apps, and I provide below some
excerpts. I include the open and most stat commands:
startx:
execve("/usr/X11R6/bin/startx", ["startx"], [/* 17 vars */]) = 0
brk(0) = 0x80b44dc
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 4
open("/lib/libreadline.so.2", O_RDONLY) = 4
open("/lib/libncurses.so.4", O_RDONLY) = 4
open("/lib/libdl.so.2", O_RDONLY) = 4
open("/lib/libc.so.6", O_RDONLY)= 4
open("/dev/tty", O_RDWR|O_NONBLOCK) = 4
stat("/usr/local/sbin/sh", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/local/bin/sh", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/sbin/sh", 0xbaa4)= -1 ENOENT (No such file or
directory)
stat("/usr/bin/sh", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/sbin/sh", 0xbaa4)= -1 ENOENT (No such file or
directory)
stat("/bin/sh", {st_dev=makedev(3, 66), st_ino=9756,
st_mode=S_IFREG|0755, st_nlink=1, open("/usr/X11R6/bin/startx",
O_RDONLY) = 4
stat("/root/.xinitrc", 0xba9c) = -1 ENOENT (No such file or
directory)
stat("/usr/X11R6/lib/X11/xinit/xinitrc", {st_dev=makedev(3, 8),
st_ino=125329, st_mode=S_IFREG|0444, st_nlink=1, st_uid=0, st_gid=10,
st_blksize=4096, st_blocks=2, st_size=666, st_atime=100/06/11-12:57:05,
st_mtime=100/01/08-09:09:58, st_ctime=100/06/09-17:27:04}) = 0
stat("/root/.xserverrc", 0xba9c)= -1 ENOENT (No such file or
directory)
stat("/usr/X11R6/lib/X11/xinit/xserverrc", 0xba20) = -1 ENOENT (No
such file or directory)
stat("/usr/local/sbin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/local/bin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/sbin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/bin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/sbin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/bin/xinit", 0xbaa4) = -1 ENOENT (No such file or
directory)
stat("/usr/X11R6/bin/xinit", {st_dev=makedev(3, 8), st_ino=113,
st_mode=S_IFREG|0755, st_nlink=1, st_uid=0, st_gid=10, st_blksize=4096,
st_blocks=22, st_size=10612, st_atime=100/06/11-12:40:52,
st_mtime=100/01/08-09:09:57, st_ctime=100/06/09-17:26:46}) = 0
stat("/usr/X11R6/bin/xinit", {st_dev=makedev(3, 8), st_ino=113,
st_mode=S_IFREG|0755, st_nlink=1, st_uid=0, st_gid=10, st_blksize=4096,
st_blocks=22, st_size=10612, st_atime=100/06/11-12:40:52,
st_mtime=100/01/08-09:09:57, st_ctime=100/06/09-17:26:46}) = 0
_exit(139) = ?
XF86Setup:
execve("/usr/X11R6/bin/XF86Setup", ["XF86Setup"], [/* 17 vars */]) = 0
brk(0) = 0x8178c10
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 4
open("/usr/X11R6/lib/Xaw3d/libXaw.so.6", O_RDONLY) = -1 ENOENT (No such
file or directory)
open("/lib/libXaw.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libXmu.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libXt.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libSM.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libICE.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libXext.so.6", O_RDONLY) = 4
open("/usr/X11R6/lib/libX11.so.6", O_RDONLY) = 4
open("/lib/libm.so.6", O_RDONLY)= 4
open("/lib/li
Segmentation fault
I get the message "Segmentation fault" when attempting to run xf86config, XF86Setup, xstart, and xinit. No other information is given. It started after I installed gpm_1.14-3.deb, although that may not be the cause of the problem. I remove gpm but still get the error. Does anyone know any more about segmentation faults? What causes them? __ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com
Re: segmentation fault
On Tue, May 30, 2000 at 11:20:38PM +0200, Smith, Martin wrote: > I installed XFree86 and when I execute startx I get: > > /usr/bin/X11/startx: line 74: 141 Segmentation faultxinit $clientargs > -- $serverargs > > Also get "segmentation fault" when I try to run XF86Setup. Any ideas what > the cause is? Probably a memory allocation error If you can capture error output to a file, do this and post it: startx -- 1>startx.log 2>&1 & You might also run strace and show any relevent output, usually near the end of the run (DON'T post the whole thing), which can provide illumination: strace startx -- Karsten M. Self http://www.netcom.com/~kmself Evangelist, Opensales, Inc. http://www.opensales.org What part of "Gestalt" don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/ K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgpTeNKTrU8v4.pgp Description: PGP signature
segmentation fault
I installed XFree86 and when I execute startx I get: /usr/bin/X11/startx: line 74: 141 Segmentation faultxinit $clientargs -- $serverargs Also get "segmentation fault" when I try to run XF86Setup. Any ideas what the cause is?
Re: segmentation fault
On Tue, May 02, 2000 at 03:45:21AM +0200, Pocsaji Miklós wrote: > Hello, > > I've got a problem with 'su': when I want to change to root, I type in a > correct password & I get a 'Segmentation fault' message. I am almost a > beginner in the Linux world, so I am fully confused. > A segmentation fault usually means that the program has a bug in it. However in your situation I would imagine that you have some faulty memory. Try running the memtest program and see what happens. Pete
Re: gedit Crash: Segmentation fault
Hmm, I just did apt-get install gedit (version 0.5.4-1) and it works fine on my machine. Only thing I would suggest is perhaps purge any trace of gedit that you currently have, and install it again. The problem might be more critical than this (ie. might be more GTk related than gEdit related) but its something to try, since its only a 150k package. Cheers, Corey Popelier http://members.dingoblue.net.au/~pancreas Work Email: [EMAIL PROTECTED] On Fri, 12 May 2000, Jaume Teixi wrote: > hi to everyone, > gedit crashed and after reisntalling it continues with crashing at > starting up it. > > fatal error (segmentation fault) > > Gtk-CRITICAL **; file gtkbox.c: line 332 (gtk_box_pack_start): assertion > `child->parent == NULL' failed. > > > any points on howto fix it ? > > thanks, > jaume > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
gedit Crash: Segmentation fault
hi to everyone, gedit crashed and after reisntalling it continues with crashing at starting up it. fatal error (segmentation fault) Gtk-CRITICAL **; file gtkbox.c: line 332 (gtk_box_pack_start): assertion `child->parent == NULL' failed. any points on howto fix it ? thanks, jaume
segmentation fault
Hello, I've got a problem with 'su': when I want to change to root, I type in a correct password & I get a 'Segmentation fault' message. I am almost a beginner in the Linux world, so I am fully confused. Thanks your help in advance: Pocsaji Miklos (Mike) Technical University of Budapest EMail: [EMAIL PROTECTED]
Segmentation Fault?
Hello. I'm a new user. Installed Debian 2.1r5 base and loaded XFree86 (unsure of version...I got the one from the "current" folder on freesoftware.com). Whenever I try to run X, or SuperProbe, or any other item in the /usr/X11R6/bin folder, I get a Sementation Fault error. What am I doing wrong? -c ___ Get 100% FREE Internet Access powered by Excite Visit http://freelane.excite.com/freeisp
Re: Wordperfect segmentation fault
> "James" == James Sleeman <[EMAIL PROTECTED]> writes: > I have never been able to get WP or Adobe Acrobat reader to > work under Debian (neither Slink, nor Potato), they both > just segfault, I thought it was just a debian peculiarity, > possibly to do with libc5 which I understand is slightly > modified in debian packaged, but if you have had it working > then I guess something really wierd must be going on with > my system because I havn't noticed any other problems. I found that acroread, wordperfect and rvplayer segfaulted on my slink system when I was using the XFCom_Rage128 xserver (installed from the RPMs with alien). The source of the segfaults was that I'd added the regframe library to /etc/ld.so.preloads. If this is what is causing your problem, I know of two ways to resolve this problem: A fix that works for slink is to arrange for the preload to be seen only by the xserver. This can be done by removing the entry in /etc/ld.so.preloads and adding a LD_PRELOAD line to your /etc/init.d/xdm script. See /usr/doc/regframe/copyright for details. For potato, you can remove the alien packages and use the Debian XFree86 3.3.6 packages, including the xserver-rage128 package. Mike
Re: Wordperfect segmentation fault
On Wed, 23 Feb 2000, James Sleeman wrote: > ---Reply to mail from Johann Spies about Wordperfect segmentation fault > > I use Wordperfect from time to time and suddenly today I get a > > segmentation fault every time try it. I worked a few days ago. > > > > I have during the past weeks upgraded some packages on my slink system to > > potato. How can I find out what is causing the problem? Maybe one of the > > new packages has removed something Wordperfect was looking for? > > > > The last new package I installed was wine. Could that break Wordperfect? > > > > I have never been able to get WP or Adobe Acrobat reader to work under > Debian (neither Slink, nor Potato), they both just segfault, I thought it > was just a debian peculiarity, possibly to do with libc5 which I > understand is slightly modified in debian packaged, but if you have had it > working then I guess something really wierd must be going on with my system > because I > havn't noticed any other problems. No I did not have that kind of problems. Up to a few days ago I could run WP without a problem and I still use Acoread 4 from potato without a problem. I really hope somebody can help me here. Johann. -- Johann Spies,Windsorlaan 19, Pietermaritzburg, 3201, South Africa Tel/Faks 033-346-1310 Sel/Cell 082-255-2388 "All scripture is given by inspiration of God, and is profitable for doctrine, for reproof, for correction, for instruction in righteousness; That the man of God may be perfect, thoroughly furnished unto all good works." II Timothy 3:16,17
Re: Wordperfect segmentation fault
---Reply to mail from Johann Spies about Wordperfect segmentation fault > I use Wordperfect from time to time and suddenly today I get a > segmentation fault every time try it. I worked a few days ago. > > I have during the past weeks upgraded some packages on my slink system to > potato. How can I find out what is causing the problem? Maybe one of the > new packages has removed something Wordperfect was looking for? > > The last new package I installed was wine. Could that break Wordperfect? > I have never been able to get WP or Adobe Acrobat reader to work under Debian (neither Slink, nor Potato), they both just segfault, I thought it was just a debian peculiarity, possibly to do with libc5 which I understand is slightly modified in debian packaged, but if you have had it working then I guess something really wierd must be going on with my system because I havn't noticed any other problems.
Wordperfect segmentation fault
I use Wordperfect from time to time and suddenly today I get a segmentation fault every time try it. I worked a few days ago. I have during the past weeks upgraded some packages on my slink system to potato. How can I find out what is causing the problem? Maybe one of the new packages has removed something Wordperfect was looking for? The last new package I installed was wine. Could that break Wordperfect? Johann -- Johann Spies,Windsorlaan 19, Pietermaritzburg, 3201, South Africa Tel/Faks 033-346-1310 Sel/Cell 082-255-2388 "The LORD bless thee, and keep thee; The LORD make his face shine upon thee, and be gracious unto thee; The LORD lift up his countenance upon thee, and give thee peace." Numbers 6:24-26
Re: Segmentation fault
Thanks for all the feedback. I really don't know what the problem was here. The Title buffer was set to 80 char and the input was not 10 characters As I come up to speed, I'll get a better understanding of the nuances of gcc/g++. In the meantime, I think I'm much safer using safe practices, as below. In this particular case, it was useful for me to convert the code to c++ stream i/o, which reads very straightforwardly. I've since enhanced it with cgi code and it now outputs the results of its computation to a web page. For instance, the code below reads in>>Title; in>>m>>n>>it>>LT>>EQ>>GT; This will change again as I hand off the interface to the client terminal David - Original Message - From: Eric G . Miller To: Sent: Tuesday, February 15, 2000 8:10 PM Subject: Re: Segmentation fault > On Tue, Feb 15, 2000 at 11:08:21PM +0900, Junichi Uekawa wrote: > > On Mon, 14 Feb 2000 11:43:25 -0800, "davidturetsky" > > <[EMAIL PROTECTED]> was crying out from somewhere about: Re: > > Segmentation fault > > > > davidturetsky> I believe this is the code > >> that was getting me into trouble, but it could be > > davidturetsky> elsewhere > > davidturetsky> > > davidturetsky> fscanf (file, "%s", Title); > > davidturetsky> fscanf (file, "%d %d %d %d %d %d", > >> &m, &n, &it, <, &EQ, >); > > > Probably, the input string was too long for the char* Title? I don't > > know. MSC seems to let the stack be destroyed quite quietly. It's a > > feature, methinks. Not too many segfaults when developing, but > > occasional BOD on using. > > This is why, I think, that fgets is recommended over scanf/fscanf. > You'll always know the maximum of the data you read in. Of course, then > you still have to split it and check your input data matches what you > expected to receive. Also, newlines and whitespace can pile up in > scanf/fscanf. It's generally recognized as being unsafe (like C/C++ in > general!). >
Re: Segmentation fault
On Tue, Feb 15, 2000 at 11:08:21PM +0900, Junichi Uekawa wrote: > On Mon, 14 Feb 2000 11:43:25 -0800, "davidturetsky" > <[EMAIL PROTECTED]> was crying out from somewhere about: Re: > Segmentation fault > davidturetsky> I believe this is the code >> that was getting me into trouble, but it could be > davidturetsky> elsewhere > davidturetsky> > davidturetsky> fscanf (file, "%s", Title); > davidturetsky> fscanf (file, "%d %d %d %d %d %d", >> &m, &n, &it, <, &EQ, >); > Probably, the input string was too long for the char* Title? I don't > know. MSC seems to let the stack be destroyed quite quietly. It's a > feature, methinks. Not too many segfaults when developing, but > occasional BOD on using. This is why, I think, that fgets is recommended over scanf/fscanf. You'll always know the maximum of the data you read in. Of course, then you still have to split it and check your input data matches what you expected to receive. Also, newlines and whitespace can pile up in scanf/fscanf. It's generally recognized as being unsafe (like C/C++ in general!). -- ++ | Eric G. Milleregm2@jps.net | | GnuPG public key: http://www.jps.net/egm2/gpg.asc | ++
Re: Segmentation fault
On Mon, 14 Feb 2000 11:43:25 -0800, "davidturetsky" <[EMAIL PROTECTED]> was
crying out from somewhere
about: Re: Segmentation fault
davidturetsky> I believe this is the code that was getting me into trouble, but
it could be
davidturetsky> elsewhere
davidturetsky>
davidturetsky> fscanf (file, "%s", Title);
davidturetsky> fscanf (file, "%d %d %d %d %d %d", &m, &n, &it, <, &EQ,
>);
Probably, the input string was too long for the char* Title?
I don't know. MSC seems to let the stack be destroyed quite quietly.
It's a feature, methinks. Not too many segfaults when developing, but
occasional BOD on using.
davidturetsky> Thanks, dancer. BTW, what's wrong with your code sample? I can
see this is
davidturetsky> going to be daunting!
davidturetsky> > For example, this code segfaults on Linux, which used to work
perfectly
davidturetsky> fine on MSC:
davidturetsky> >
davidturetsky> > char * bitsofmemory = malloc (BIG_SIZE); FILE*f
=fopen(FILENAME,
davidturetsky> ATTRIBUTE);
davidturetsky> > if (!(bitsofmemory && f)) {
davidturetsky> >free(bitsofmemory); fclose(f) /* try to clean up and it
dies...*/
davidturetsky> >return ERROR;
davidturetsky> > }
It it meant to free up the allocated memory space and the file handle when
either operation
fails (a kind of expression found at the beginning of many functions). But one
is trying to
free up a NULL pointer, and that probably means read/write to a
location where it is probably (or hopefully) not allocated to the program.
Either the MS library checks for NULL every time it is called (I think that's
kinda nice, but
then, it is a waste), or NULL might be a place you can dump things on.
One thing. To make it run on Linux, I had to change it to:
davidturetsky> > if (!(bitsofmemory && f)) {
davidturetsky> >if (bitsofmemory)free(bitsofmemory); if(f)fclose(f) /* try
to clean up and it dies...*/
davidturetsky> >return ERROR;
davidturetsky> > }
---
dancer, a.k.a. Junichi Uekawa
a member of the Dept. of Knowledge Engineering and Computer Science,
Doshisha University.
... I pronounce "Linux" as in [Day-bee-enne]
Re: Segmentation fault
davidturetsky wrote:
>
> I believe this is the code that was getting me into trouble, but it could be
> elsewhere
>
> fscanf (file, "%s", Title);
This one may get you into trouble if the Title array is not large enough
to hold the string.
> fscanf (file, "%d %d %d %d %d %d", &m, &n, &it, <, &EQ, >);
This looks okay.
>
> I was always uncomfortable with the notation esthetically, so I took
> advantage of the occasion to change all the i/o to stream style
> Once I got rid of "using namespace" it ran fine
>
> Don't go away. I'll be back whining about some other problem!
>
> Thanks, dancer. BTW, what's wrong with your code sample? I can see this is
> going to be daunting!
> > char * bitsofmemory = malloc (BIG_SIZE); FILE*f =fopen(FILENAME,
> ATTRIBUTE);
> > if (!(bitsofmemory && f)) {
> >free(bitsofmemory); fclose(f) /* try to clean up and it dies...*/
> >return ERROR;
> > }
This code tries to do both free the memory and close the file regardless
of which caused the error. A much neater and more readable version would
be:
char * bitsofmemory = malloc (BIGSIZE);
FILE * f = fopen(FILENAME, ATTRIBUTE);
if (bitsofmemory == NULL || f == NULL)
{
if (bitsofmemory != NULL)
{
free(bitsofmemory);
}
if (f != NULL)
{
fclose(f);
}
}
Matthew
Re: Segmentation fault
On Mon, Feb 14, 2000 at 11:43:25AM -0800, davidturetsky wrote:
>
> Thanks, dancer. BTW, what's wrong with your code sample? I can see this is
> going to be daunting!
It dies when it tries to fclose the NULL pointer (fopen returns NULL
when it fails). free causes no trouble since it does nothing with NULL
according to the manpage. i wonder why fclose doesn't handle the problem
more gracefully in the NULL case?
Anyway, s/fclose(f)/if(f) fclose(f);/ to fix it.
> - Original Message -
> From: Junichi Uekawa <[EMAIL PROTECTED]>
> >
> > For example, this code segfaults on Linux, which used to work perfectly
> fine on MSC:
> >
> >
> > char * bitsofmemory = malloc (BIG_SIZE); FILE*f =fopen(FILENAME,
> ATTRIBUTE);
> > if (!(bitsofmemory && f)) {
> >free(bitsofmemory); fclose(f) /* try to clean up and it dies...*/
Missing semicolon? ^
> >return ERROR;
> > }
--
finger for GPG public key.
8 Jan 2000 - Old email addresses removed from key, new added
pgplucs5cdCxd.pgp
Description: PGP signature
Re: Segmentation fault
I believe this is the code that was getting me into trouble, but it could be
elsewhere
fscanf (file, "%s", Title);
fscanf (file, "%d %d %d %d %d %d", &m, &n, &it, <, &EQ, >);
I was always uncomfortable with the notation esthetically, so I took
advantage of the occasion to change all the i/o to stream style
Once I got rid of "using namespace" it ran fine
Don't go away. I'll be back whining about some other problem!
Thanks, dancer. BTW, what's wrong with your code sample? I can see this is
going to be daunting!
David
- Original Message -
From: Junichi Uekawa <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
Sent: Sunday, February 13, 2000 9:56 PM
Subject: Re: Segmentation fault
> On Sun, 13 Feb 2000 03:45:55 -0800, "davidturetsky"
<[EMAIL PROTECTED]> was crying out from somewhere
> about: Re: Segmentation fault
>
> davidturetsky> It looks as though I was running into problems when trying
to scan an input
> davidturetsky> file using c notation which is less efficient of memory, so
I'm in the
> davidturetsky> process of revising all of the I/O to use c++ resources.
Still, it comes as
> davidturetsky> a surprise, but I'm very early on the gcc learning curve
>
>
> Reading this I am wondering if you actually did allocate memory for the
variables, or even did you do the right thing?
>
> for example, getting input for a double with scanf will require you doing
something like
>
> double a;
> scanf("%g", &a);
>
> You can even do double a; scanf("%g", a); and it might still work on MS
compiler, it won't on gcc.
>
>
> That was my personal experience migrating my own code.
> I found many invalid pointers in my code.
> MSC seems to be very "relaxed" in handling invalid pointers.
> Linux is very harsh and kills your app with a segfault as soon as you try
to
> access it.
>
> For example, this code segfaults on Linux, which used to work perfectly
fine on MSC:
>
>
> char * bitsofmemory = malloc (BIG_SIZE); FILE*f =fopen(FILENAME,
ATTRIBUTE);
> if (!(bitsofmemory && f)) {
>free(bitsofmemory); fclose(f) /* try to clean up and it dies...*/
>return ERROR;
> }
Re: Segmentation fault
On Sun, 13 Feb 2000 03:45:55 -0800, "davidturetsky" <[EMAIL PROTECTED]> was
crying out from somewhere
about: Re: Segmentation fault
davidturetsky> It looks as though I was running into problems when trying to
scan an input
davidturetsky> file using c notation which is less efficient of memory, so I'm
in the
davidturetsky> process of revising all of the I/O to use c++ resources. Still,
it comes as
davidturetsky> a surprise, but I'm very early on the gcc learning curve
Reading this I am wondering if you actually did allocate memory for the
variables, or even did you do the right thing?
for example, getting input for a double with scanf will require you doing
something like
double a;
scanf("%g", &a);
You can even do double a; scanf("%g", a); and it might still work on MS
compiler, it won't on gcc.
That was my personal experience migrating my own code.
I found many invalid pointers in my code.
MSC seems to be very "relaxed" in handling invalid pointers.
Linux is very harsh and kills your app with a segfault as soon as you try to
access it.
For example, this code segfaults on Linux, which used to work perfectly fine on
MSC:
char * bitsofmemory = malloc (BIG_SIZE); FILE*f =fopen(FILENAME, ATTRIBUTE);
if (!(bitsofmemory && f)) {
free(bitsofmemory); fclose(f) /* try to clean up and it dies...*/
return ERROR;
}
---
Junichi Uekawa, a.k.a. dancer
a member of the Dept. of Knowledge Engineering and Computer Science,
Doshisha University.
... I pronounce "Linux" as [Day-bee-enne]
Re: Segmentation fault
Yes, quite right. I was not being critical of gcc, but of my own coding orientation. I've reached similar conclusions as you outline There is a rather large body of material I desperately need to read and absorb. That's exactly the problem I'm trying to contend with in trying to convert my work to Linux/gcc/x/ppp... and why some gentle assists from the list are so useful in helping me get started David - Original Message - From: Colin Watson <[EMAIL PROTECTED]> To: Sent: Sunday, February 13, 2000 2:54 AM Subject: Re: Segmentation fault > [EMAIL PROTECTED] (davidturetsky) wrote: > >I see from further investigation that gcc wants me to be more actively > >concerned with memory management than was required under Visual C, and I was > >logging on to apologize for bothering the list. I posted because this code > >ran cleanly under Visual C, so I thought I ran into a Linux nuance > > > >It looks as though I was running into problems when trying to scan an input > >file using c notation which is less efficient of memory, so I'm in the > >process of revising all of the I/O to use c++ resources. > > This surprises me; I'd have thought stdio was more memory-efficient than > iostreams, if it's an issue at all (which I rather doubt). Regardless, a > segmentation fault is an indication of a memory access bug in your > program rather than running out of memory (it may not have happened in > Visual C simply because you were lucky in the way Visual C allocated > memory for you), so you may be trying to fix the wrong problem by doing > all this rewriting. (Of course, you may be lucky and accidentally fix it > in the process, or the problem may have been that you didn't know how to > use stdio and are more successful in using iostreams, but I suppose it > depends whether you actually want to know what you're doing ...) > > >In general, I am beginning to notice that gcc's posture is that you do more > >for yourself. It also seems to be strictly limited to ANSI c. For example, > >there doesn't seem to be any support for min, max, and itoa and I ended up > >writing/rewriting that portion of the code > > I think you desperately need to read 'info gcc' and 'info libc'. gcc is > notoriously far from limited to ANSI C. :) > > Actually, your problem is not with gcc, it seems to be that the GNU C > Library (libc/glibc) doesn't have what you want; it's far from limited > to ANSI C either, but any C programmer worth his/her salt knows that if > you use extensions in your code you should expect them not to be > portable. glibc simply has different extensions to Visual C; in general > I've found it a much more helpful and much better documented C library > than the Microsoft one, but I may be biased. > > Besides, min(), max(), and itoa() are hardly difficult. How about: > > #define min(a,b) ((a) < (b) ? (a) : (b)) > #define max(a,b) ((a) > (b) ? (a) : (b)) > > ... or equivalent function definitions if the double evaluation bothers > you, and sprintf() instead of itoa()? If you program in ANSI C wherever > possible to start with rather than lazily using extensions, you'll have > a much easier time of it.
Re: Segmentation fault
[EMAIL PROTECTED] (davidturetsky) wrote: >I see from further investigation that gcc wants me to be more actively >concerned with memory management than was required under Visual C, and I was >logging on to apologize for bothering the list. I posted because this code >ran cleanly under Visual C, so I thought I ran into a Linux nuance > >It looks as though I was running into problems when trying to scan an input >file using c notation which is less efficient of memory, so I'm in the >process of revising all of the I/O to use c++ resources. This surprises me; I'd have thought stdio was more memory-efficient than iostreams, if it's an issue at all (which I rather doubt). Regardless, a segmentation fault is an indication of a memory access bug in your program rather than running out of memory (it may not have happened in Visual C simply because you were lucky in the way Visual C allocated memory for you), so you may be trying to fix the wrong problem by doing all this rewriting. (Of course, you may be lucky and accidentally fix it in the process, or the problem may have been that you didn't know how to use stdio and are more successful in using iostreams, but I suppose it depends whether you actually want to know what you're doing ...) >In general, I am beginning to notice that gcc's posture is that you do more >for yourself. It also seems to be strictly limited to ANSI c. For example, >there doesn't seem to be any support for min, max, and itoa and I ended up >writing/rewriting that portion of the code I think you desperately need to read 'info gcc' and 'info libc'. gcc is notoriously far from limited to ANSI C. :) Actually, your problem is not with gcc, it seems to be that the GNU C Library (libc/glibc) doesn't have what you want; it's far from limited to ANSI C either, but any C programmer worth his/her salt knows that if you use extensions in your code you should expect them not to be portable. glibc simply has different extensions to Visual C; in general I've found it a much more helpful and much better documented C library than the Microsoft one, but I may be biased. Besides, min(), max(), and itoa() are hardly difficult. How about: #define min(a,b) ((a) < (b) ? (a) : (b)) #define max(a,b) ((a) > (b) ? (a) : (b)) ... or equivalent function definitions if the double evaluation bothers you, and sprintf() instead of itoa()? If you program in ANSI C wherever possible to start with rather than lazily using extensions, you'll have a much easier time of it. >Is there a separate users group for gcc? gnu.gcc.help? HTH, -- Colin Watson [EMAIL PROTECTED]
Re: Segmentation fault
Thanks, Pete I see from further investigation that gcc wants me to be more actively concerned with memory management than was required under Visual C, and I was logging on to apologize for bothering the list. I posted because this code ran cleanly under Visual C, so I thought I ran into a Linux nuance It looks as though I was running into problems when trying to scan an input file using c notation which is less efficient of memory, so I'm in the process of revising all of the I/O to use c++ resources. Still, it comes as a surprise, but I'm very early on the gcc learning curve This is a large theoretical problem I was attacking so my initial preference was not to alter anything that didn't requiring fixing, but the code is certainly cleaner after reworking In general, I am beginning to notice that gcc's posture is that you do more for yourself. It also seems to be strictly limited to ANSI c. For example, there doesn't seem to be any support for min, max, and itoa and I ended up writing/rewriting that portion of the code BTW, I notices that my non-working install of XFree86 3.3.6 (?) is also generating Segmentation faults, suggestive of bugs in the newest release. I've posted this to their developers Is there a separate users group for gcc? David - Original Message - From: Peter Ross <[EMAIL PROTECTED]> To: davidturetsky <[EMAIL PROTECTED]> Cc: Sent: Saturday, February 12, 2000 11:05 PM Subject: Re: Segmentation fault > On 13-Feb-2000, davidturetsky <[EMAIL PROTECTED]> wrote: > > I am executing a Linear Program program I wrote and compiled. It > > terminates without generating output (but creates the output file) > > with a "Segmentation fault" > > > A segmentation fault occurs when you attempt to access memory that you > are not allowed to (usually deferencing an invalid pointer). > > > I'm trying to convert programs to run under g++ which I previously > > developed using Visual c 5.0 and would appreciate any help in sorting > > this out > > > > Is there a log which is generated which might provide further details? > > > You can compile with the -g switch to turn debugging on, and then use > gdb to debug the program, and it will tell you which line caused the seg > fault. > > Pete
Re: Segmentation fault
On 13-Feb-2000, davidturetsky <[EMAIL PROTECTED]> wrote: > I am executing a Linear Program program I wrote and compiled. It > terminates without generating output (but creates the output file) > with a "Segmentation fault" > A segmentation fault occurs when you attempt to access memory that you are not allowed to (usually deferencing an invalid pointer). > I'm trying to convert programs to run under g++ which I previously > developed using Visual c 5.0 and would appreciate any help in sorting > this out > > Is there a log which is generated which might provide further details? > You can compile with the -g switch to turn debugging on, and then use gdb to debug the program, and it will tell you which line caused the seg fault. Pete
Re: Segmentation fault
On Sun, 13 Feb 2000, davidturetsky wrote: davidt >I am executing a Linear Program program I wrote and compiled. It terminates without generating output (but creates the output file) with a "Segmentation fault" davidt > davidt >I'm trying to convert programs to run under g++ which I previously developed using Visual c 5.0 and would appreciate any help in sorting this out davidt > davidt >Is there a log which is generated which might provide further details? while im not a programmer, using the program 'strace' can probably help provide more info on the problem. strace is in package 'strace' in slink(not sure about potato) the format is: strace you may want to dump the outpuit to a file as it is quite verbose: strace command >&strace.log & tail -f strace.log nate [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 10:55pm up 177 days, 11:11, 1 user, load average: 0.34, 0.08, 0.02
Segmentation fault
I am executing a Linear Program program I wrote and compiled. It terminates without generating output (but creates the output file) with a "Segmentation fault" I'm trying to convert programs to run under g++ which I previously developed using Visual c 5.0 and would appreciate any help in sorting this out Is there a log which is generated which might provide further details? David
Apple rtsp_proxy gives segmentation fault
Hi, all. I would like to use Quicktime streaming over my cable modem from my Mac and Windoze machines. Apple offers a rtsp_proxy (possibly also useful with Real and/or MS streaming as well, but I don't know) for linux. I downloaded, installed and launched it successfully, but when I try to hit it, I get a segmentation fault. I have tried dejanews and other internet searches without finding a reference to this. I am running 2.2 kernel, and all my internet stuff works just great. I am using NAT on it; perhaps it is interfering with the UDP or TCP stuff that the rtsp_proxy is trying to do. So have you gotten this to work? And do I need to adjust my ipchains if I am running the proxy on the NAT machine? TIA Guyren G Howe
Re: segmentation fault
If it were reproduceable (maybe you should ask someone else to reproduce it -- not me though as I'm not running potato) I would suck and install the latest deb and report a bug if the seg-fault is still there...
segmentation fault
just installed
linuxconf, but then i try to
start it reports:
Segmentation fault.
How could I reinstall it correctly?
|{.f|.
Re: Segmentation Fault
*- On 2 Jan, Rik Burt wrote about "Segmentation Fault" > I have the slink version of debian installed an a second hard drive and it > was working quite well. At the start of December I recompiled the kernel as > I had added a SCSI device to my system and as the kernel was compiling I got > an error "Segmentation Fault." These messages are becoming increasingly > more common. Last night I was looking at going to potato but apt-get update > kept breaking and saying "Segmentation Fault". This is making my Linux > experience miserable. I have been reading everything I have but can not > determine if this is a Software or Hardware problem. Any one else ever had > this. > Sounds like a hardware problem, most likely bad memory. Take a look at the Sig11 page and see if the info on there helps you find the problem. http://www.bitwizard.nl/sig11/ Brian Servis -- Mechanical Engineering | Never criticize anybody until you Purdue University | have walked a mile in their shoes, [EMAIL PROTECTED] | because by that time you will be a http://www.ecn.purdue.edu/~servis | mile away and have their shoes.
Segmentation Fault
I have the slink version of debian installed an a second hard drive and it was working quite well. At the start of December I recompiled the kernel as I had added a SCSI device to my system and as the kernel was compiling I got an error "Segmentation Fault." These messages are becoming increasingly more common. Last night I was looking at going to potato but apt-get update kept breaking and saying "Segmentation Fault". This is making my Linux experience miserable. I have been reading everything I have but can not determine if this is a Software or Hardware problem. Any one else ever had this.
