Ed Cogburn wrote:
>
>
> Ok, I'll get ps compiled with debugging info and try again.
> I'll get back to ya. (This oughta be fun)
Well, not as much fun as I thought. I downloaded the procps source
from debian woody (plus diff). I modified the Makefiles to remove "-O2"
and a
Chris Gray wrote:
>
Thanks for helping Chris.
> > Ed Cogburn writes:
>
> ec> Athlon "Thunderbird" CPU, 1Ghz
>
> You lucky bastard.
You don't want to know what a 1Ghz Athlon plus an Ultra160 SCSI drive
can do for kernel compiles! By the time you're back from
> Ed Cogburn writes:
ec> Thanks guys for the help.
ec> Ok first, my CPU is not overclocked. My hardware is
ec> all fairly new though, so I'll list the major components:
ec> Athlon "Thunderbird" CPU, 1Ghz
You lucky bastard.
ec> Fourth, t
Thanks guys for the help.
Ok first, my CPU is not overclocked. My hardware is all fairly new
though, so I'll list the major components:
Athlon "Thunderbird" CPU, 1Ghz
Asus A7V mobo
Adaptec Ultra160 SCSI card
18Gb Seagate SCSI drive
"Geforc
Chris Gray <[EMAIL PROTECTED]> wrote:
>> Gary Hennigan writes:
>
>gh> "Ed Cogburn" <[EMAIL PROTECTED]> writes:
>>>>
>>>>
>>>> This is what I get with an strace on ps:
>>>>
>>>>
>gh> [snip]
>>>> o
> Gary Hennigan writes:
gh> "Ed Cogburn" <[EMAIL PROTECTED]> writes:
>>>
>>>
>>> This is what I get with an strace on ps:
>>>
>>>
gh> [snip]
>>> open("/boot/System.map", O_RDONLY|O_NONBLOCK|O_NO
Ed Cogburn <[EMAIL PROTECTED]> wrote:
>This is what I get with an strace on ps:
[snip]
>open("/boot/System.map", O_RDONLY|O_NONBLOCK|O_NOCTTY) = 6
>fstat(6, {st_mode=S_IFREG|0664, st_size=141296, ...}) = 0
>old_mmap(NULL, 141297, PROT_READ|PROT_WRITE, MAP_PRIVATE, 6, 0) =
>0x401df000
>close(6)
"Ed Cogburn" <[EMAIL PROTECTED]> writes:
> Colin Watson wrote:
> >
> > Ed Cogburn <[EMAIL PROTECTED]> wrote:
> > > Ever seen this? Whenever I run 'ps' it says it caught 'signal 11'.
> > >The output from 'ps', aside from the signal 11 error message, is
> > >correct, the program is working ri
Colin Watson wrote:
>
> Ed Cogburn <[EMAIL PROTECTED]> wrote:
> > Ever seen this? Whenever I run 'ps' it says it caught 'signal 11'.
> >The output from 'ps', aside from the signal 11 error message, is
> >correct, the program is working right, and I'm not getting signal 11
> >from anywhere e
Ed Cogburn <[EMAIL PROTECTED]> wrote:
> Ever seen this? Whenever I run 'ps' it says it caught 'signal 11'.
>The output from 'ps', aside from the signal 11 error message, is
>correct, the program is working right, and I'm not getting signal 11
>from anywhere else, including when compiling th
Ever seen this? Whenever I run 'ps' it says it caught 'signal 11'.
The output from 'ps', aside from the signal 11 error message, is
correct, the program is working right, and I'm not getting signal 11
from anywhere else, including when compiling the kernel, only 'ps'.
Make sense to any
11 matches
Mail list logo