[6428] in Athena Bugs

home help back first fref pref prev next nref lref last post

vax 7.1: emacs, xterm

daemon@ATHENA.MIT.EDU (Ken Raeburn)
Mon Nov 19 03:07:41 1990

Date: Mon, 19 Nov 90 03:07:23 -0500
From: Ken Raeburn <Raeburn@MIT.Edu>
To: bugs@ATHENA.MIT.EDU

System name:		binkley
Type and version:	MVAX-II 7.1H
Display type:		SM

What were you trying to do?
	strings /usr/athena/emacs
	strings /etc/xterm

What's wrong:
	I got lots of text.

What should have happened:
	Most of it should have been put into the text section.

The RCS strings in the X code:

$XConsortium: Alloc.c,v 1.29 89/11/03 07:58:12 swick Exp $
$XConsortium: Convert.c,v 1.40 90/06/04 15:06:37 kit Exp $
$XConsortium: Converters.c,v 1.53 89/12/20 16:32:37 swick Exp $
$XConsortium: Create.c,v 1.74 90/07/02 16:47:25 swick Exp $
$XConsortium: Display.c,v 1.46 90/07/15 21:39:36 swick Exp $

... should either be `char *' or (preferably) `const char rcsid[]'.

A lot of strings show up from name-resolver code in the C library,
because of the debugging code compiled into it; the resolver code (and
other portions) can probably be compiled with gcc, and the RT C
library should definitely be buildable (or be fixed to be buildable)
with -Hon=read_only_strings.  (Or maybe the C library version of the
resolver shouldn't have the debugging code; how often does it get
used, other than in bindtest?  Just provide the debugging version as a
separate library....)

It might also be possible for emacs to put more stuff into the text
section (on those platforms on which it can do so), but I expect it's
already doing a fairly good job....

Lots of stuff like that in xterm also.

home help back first fref pref prev next nref lref last post