Re: [MiNT] GDB problem

["Helmut Karlowski" <helmut.karlowski@ish.de>]

Adam Klobukowski wrote:

> Your output differs from mine, You got 0 in MEM, and I got something
> like MAXLONG there. I'm using 1.17 kernel from CVS.

It's very likely to get random output when there's a /0 somewhere. I
suppose there's an incompatibility between MiNTs /kern and others /proc,
where MiNT has a 0 or nothing.

>
> Can you guys try ps axu? and top?

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0    424     0 ?        Ds   13:42   0:05 U:/home/root/KSHA.PRG
root         2  0.0  0.0     24     0 ?        S    13:42   0:00 [update]
root         3  0.0  0.0    664     0 ?        S    13:42   0:02 [fvdi_gnu]
root         6  0.0  0.0     16     0 ?        Ss   13:42   0:00 U:\c\mint\1-17-cur\xaaes\.\xaloader.prg xaaes040.km
root         7  0.0  0.0     24     0 ?        S    13:42   0:00 [AESSYS]
root         8  0.0  0.0     24     0 ?        D    13:42   0:00 [aesthred]
root         9  0.0  0.0     24     0 ?        D    13:42   0:13 [XaSYS]
root        12  0.0  0.0    392     0 ?        Ss   13:42   0:04 U:\bin\sh
root        15  0.0  0.0    560     0 ?        RN   13:42   0:01 U:/usr/gem/toswin2.app
root        16  0.0  0.0    392     0 ?        Ds   13:42   0:03 U:\bin\sh
root        18  0.0  0.0    768     0 ?        Rs   13:42   0:02 U:\f\download\procps\.\ps axu

Need to install ncurses for top first.

> Btw. IMO, the output is fine - try terminal with more columns.

Mine was prob. broken by transport.

> I'm gonna try it with 1.18 later today. The default CVS is 1.17, chow
> can I check out 1.18?

Maybe you have 1.17 installed and CVS always uses that branch, dont know.


-Helmut