public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] depscan.sh segfault issue
  @ 2001-11-11 23:46 99% ` jano
  0 siblings, 0 replies; 1+ results
From: jano @ 2001-11-11 23:46 UTC (permalink / raw
  To: gentoo-dev

Ahhhh poop, feel like a dork replying to myself.  But I made some progress.

I've narrowed down the problem to the gpm init.d script.  For some reason,
depscan doesn't like it at all.  I messed around, and found an interesting,
albeit STRANGE, pattern:

if I named gpm to:
gpm-
gpm~
gpm1
gmp
gpf
mouse
mouse-script

and tried to add it using rc-update (makeing sure it was removed first),
depscan would segfault.  However, when I named gpm to
testing
test
blah
foobar
it worked great.

I also tried commenting out everything inside the script, moving stuff
around, blah blah blah, no go.

Uhhhm.... HUH???????????????????????  This is mucked up. :D

>
> Hi,
>
> my depscan.sh segfaulting issue is still here.  I upgraded baselayout
> to next version (1.6.5 from 1.6.4), but couldn't figure out how to make
> it work.
> Per rec of some people on irc, I ran depscan.sh through strace.  Sorry,
> i have no idea how to debug a seg fault, but the output of depscan
> through strace is here, for anyone interested:
>
> http://www.portablehole.net/~jano/fridge/strace.depscan.sh.bz2
> (28k, decompresses to 3.5MB file)
>
> system specs:
> kernel 2.4.14 with preempt and xfs patches
> p3 800x2, 512MB ram
> via apollopro chipset
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev






^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2001-11-11 23:25     [gentoo-dev] depscan.sh segfault issue jano
2001-11-11 23:46 99% ` jano

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox