Re: Possible "lseek()" bug - (nf) - Article 661 - go-pugleaf

Article View: comp.bugs.sys5

Article #661

Re: Possible "lseek()" bug - (nf)

#661

From: jh
Date: Mon, 21 Dec 1987 07:34

14 lines
741 bytes

We at PCS ran into this problem, too. This is because system
addresses in /dev/kmem (maybe /dev/mem) may look like

	_entry:  0x80000400

Thus, e.g. programs like crash, ps, who etc. have to

	lseek(corefd, nlist[PROC].n_value, 0);

cannot accept an error return. How should one fix this? We opened
the respective addresses for character special files.

		Johannes Heuft
		unido!pcsbst!jh

Technical Details

Message-ID: <1200003@pcsbst.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!mcvax!unido!pcsbst!jh

References: <978@sauron.UUCP>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!mcvax!unido!pcsbst!jh
From: jh@pcsbst
Newsgroups: comp.bugs.sys5
Subject: Re: Possible "lseek()" bug - (nf)
Message-ID: <1200003@pcsbst.UUCP>
Date: 21 Dec 87 07:34:00 GMT
References: <978@sauron.UUCP>
Lines: 14
Nf-ID: #R:sauron:-97800:pcsbst:1200003:000:389
Nf-From: pcsbst!jh    Dec 21 08:34:00 1987

Reply to Parent Message