SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
01-16-2008, 07:54 AM
| ||||
| ||||
 findutils: locate seg fault hello all, i used locate from findutils on sol7, sol8 and sol9. findutils came from sunfreeware.com or blastwave.org or from sun cd companion. Sine few months, locate seg fault on sol8, and on sol9, when i launch updatedb, it runs during 2 days and consumes 100% cpu still i kill it i search on google, not finding a solution findutils is 4.1 and seems not released since 1994 i try to recompile it, but obtain the same result scr-henry% truss ./locate/locate runtest read(3, " r i m e n t A T - t h e".., 8192) = 8192 read(3, " t o . e p s\0\n f i g\0".., 8192) = 8192 Incurred fault #6, FLTBOUNDS %pc = 0x000124DC siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 Received signal #11, SIGSEGV [default] siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 *** process killed *** anybody can help? gerard      |
|
01-16-2008, 07:54 AM
| |||
| |||
| Re: findutils: locate seg fault 2004-10-07, 14:57(+02), jdh13: > hello all, > i used locate from findutils on sol7, sol8 and sol9. > findutils came from sunfreeware.com or blastwave.org or from sun cd > companion. > Sine few months, locate seg fault on sol8, and on sol9, when i launch > updatedb, it runs during 2 days and consumes 100% cpu still i kill it > i search on google, not finding a solution > findutils is 4.1 and seems not released since 1994 [...] There's a 4.1.20 somewhere on alpha.gnu.org, that's the one usually shipped with Linux distribution. But GNU locate is mostly broken, you may prefer installing slocate (ftp://ftp.geekreview.org/slocate/) (not tested but you find that one as a replacement for GNU locate on many Linux distributions) or AT&T tw (a replacement for find) (you can find it in the ast-open package http://www.research.att.com/~gsf/dow.../ast-open.html) Alternatively, you can run a find / | gzip > some-file.gz, and have a simple locate script that does a zgrep on that file (it's generally more efficient than GNU locate). -- Stephane |
|
01-16-2008, 07:54 AM
| |||
| |||
| Re: findutils: locate seg fault On Thu, 7 Oct 2004, jdh13 wrote: > hello all, > i used locate from findutils on sol7, sol8 and sol9. > findutils came from sunfreeware.com or blastwave.org or from sun cd > companion. > Sine few months, locate seg fault on sol8, and on sol9, when i launch > updatedb, it runs during 2 days and consumes 100% cpu still i kill it > i search on google, not finding a solution > findutils is 4.1 and seems not released since 1994 > > i try to recompile it, but obtain the same result ../configure --program-prefix=g please : > > scr-henry% truss ./locate/locate runtest > > read(3, " r i m e n t A T - t h e".., 8192) = 8192 > read(3, " t o . e p s\0\n f i g\0".., 8192) = 8192 > Incurred fault #6, FLTBOUNDS %pc = 0x000124DC > siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 > Received signal #11, SIGSEGV [default] > siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 > *** process killed *** > anybody can help? Maybe. You will get seg faults when you dont alter PRUNEPATHS to include directories like /proc... eg: : ${PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /proc"} |
|
01-16-2008, 07:56 AM
| |||
| |||
| Re: findutils: locate seg fault Gerry wrote: > On Thu, 7 Oct 2004, jdh13 wrote: > > >>hello all, >>i used locate from findutils on sol7, sol8 and sol9. >>findutils came from sunfreeware.com or blastwave.org or from sun cd >>companion. >>Sine few months, locate seg fault on sol8, and on sol9, when i launch >>updatedb, it runs during 2 days and consumes 100% cpu still i kill it >>i search on google, not finding a solution >>findutils is 4.1 and seems not released since 1994 >> >>i try to recompile it, but obtain the same result > > > ./configure --program-prefix=g please : > > it depends, on sunfreeware, there isn't "g", on blastwave, yes >>scr-henry% truss ./locate/locate runtest >> >>read(3, " r i m e n t A T - t h e".., 8192) = 8192 >>read(3, " t o . e p s\0\n f i g\0".., 8192) = 8192 >> Incurred fault #6, FLTBOUNDS %pc = 0x000124DC >> siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 >> Received signal #11, SIGSEGV [default] >> siginfo: SIGSEGV SEGV_MAPERR addr=0x000363C3 >> *** process killed *** >>anybody can help? > > > Maybe. You will get seg faults when you dont alter PRUNEPATHS > to include directories like /proc... eg: > : ${PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /proc"} > great! many thanks it works now! i did: updatedb --prunepaths='/tmp /usr/tmp /var/tmp /home /proc /var/run' i added /home because it's on a nfs client but it is very strange that on some machines in sol8 or sol9, it worked without "prune option"!? gerard henry |
|
01-16-2008, 07:56 AM
| ||||
| ||||
| Re: findutils: locate seg fault On Fri, 15 Oct 2004, jdh13 wrote: > Gerry wrote: > > On Thu, 7 Oct 2004, jdh13 wrote: > >>i used locate from findutils on sol7, sol8 and sol9. > >>findutils came from sunfreeware.com or blastwave.org or from sun cd > >>companion. > >>i try to recompile it, but obtain the same result > > ./configure --program-prefix=g please : > > > > it depends, on sunfreeware, there isn't "g", on blastwave, yes Who cares what sunfreeware does : > You compiled it so "do the right thing" : > GNU find is not Berkeley find, GNU tar is not Solaris tar etc etc. GNU is GNU /usr/local is a BSDism anyway. Solaris uses /opt. Sorry for OT preaching but this is an admin group after all. > > : ${PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /proc"} > > > great! many thanks it works now! For now : > > but it is very strange that on some machines in sol8 or sol9, it worked > without "prune option"!? You were lucky.. Given time you will get seg fault from somewhere. Use -g with gcc if you want to find the culprit. |
Linear Mode
