HDTenEightyP/NetNews huggingface dataset:
From: friedman@bnr.ca (Barry (B.L.) Friedman)
Subject: mxgdb
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 1 Jan 1993 06:10:41 GMT

Newsgroups: gnu.gdb.bug
Subject: mxgdb / can't get it to work 
Summary: 
Expires: 
Followup-To: 
Distribution: world
Organization: Northern Telecom, Ltd.
Keywords: 

I've build mxgdb as per the README using -DHAVE_TERMIO and have not
been able to get it to run.  It starts up and immediately beeps.
If I try to load an executable, it loads but does not display any
source listing.  Messages in the terminal area seem to be terminated by
a small 'upper-left-corner' line-drawing symbol.

I've probably overlooked something simple.  Crossing my fingers does
not seem to help :-)

BTW the platform is Sun OS 4.1  compiled with gcc

Thanks for any help.


	Barry Friedman
	friedman@bnr.ca

-- 
Barry Friedman                          Phone: (613) 782-2389  Fax: 782-2228
Emax Computer Systems Inc.  440 Laurier Ave. W., Ottawa, Ont. Canada K1R 5C4
INTERNET: friedman@bnr.ca                                      ESN: 395-4270

Newsgroups: gnu.gdb.bug
From: gnu@cygnus.com
Subject: Re: Configuring gdb for a mips 3240 running 4_52
Organization: GNUs Not Usenet
Distribution: gnu
Date: Mon, 4 Jan 1993 12:33:26 GMT

> I have wasted a few hours trying to run "configure" for a mips 3240
> (or 3230 for that matter, same problem).

Congratulations.  You're the proud owner of a machine that GDB does not
currently support.  It's not hard to port it, though, just tedious.
If you spent a few hours running configure, you probably have the stamina
to cope.

Look at gdb-4.7/gdb/doc/gdbint.texinfo for detailed information on how
to port GDB to a new native platform.

If you want to save other people the trouble in future, ask
gnu@prep.ai.mit.edu for the paperwork required to contribute your
changes to GDB back to the FSF.  (Since the paperwork usually takes
longer than making the changes, it's useful to start the paperwork
first.)

	John Gilmore
	GDB maintainer



Newsgroups: gnu.gdb.bug
From: hdanilev@othello.fnbc.COM (Harry Danilevsky)
Subject: GDB 4.7 on NeXT - will it work ?
Keywords: gdb, NeXT, gnu
Organization: First National Bank Of Chicago, Chicago IL, USA
Distribution: gnu
Date: Thu, 7 Jan 1993 15:28:50 GMT

I tried to install gdb 4.7 on NeXT (using 'configure next'), and
got the message :

*** opcodes does not support host m68k-next-bsd
*** BFD does not support host m68k-next-bsd
*** Gdb does not support host m68k-next-bsd

I guess, I could try to build Gdb on a Sun with target=next, but this is
not what I want.

Is it possible to get gdb 4.7 to work on NeXT, and if not, does anybody
know if FSF is planning to have a NeXT release in the reasonable future?

Thanx,

- Harry

Newsgroups: gnu.gdb.bug
From: mauro@netcom.com (Mauro DePalma)
Subject: gdb-4.7 attach problem on SUN4
Organization: GNUs Not Usenet
Distribution: gnu
Date: Tue, 5 Jan 1993 20:04:55 GMT

On a SPARCstation 1+ running SunOS 4.1.2 gdb-4.7 refuses to attach to
a process. Although the solution is trivial I haven't seen to date any
articles on this subject; for whatever it's worth to follow is a patch.

     mauro@netcom.com (member of the LPF)

*** gdb/inftarg.c-	Wed Oct  7 17:30:43 1992
--- gdb/inftarg.c	Tue Jan  5 11:36:28 1993
***************
*** 26,31 ****
--- 26,33 ----
  #include "gdbcore.h"
  #include "terminal.h"		/* For #ifdef TIOCGPGRP and new_tty */
  
+ #include "nm.h"
+ 
  #include <signal.h>
  
  static void

Newsgroups: gnu.gdb.bug
From: tmcconne@sedona.intel.com (Tom McConnell~)
Subject: Re: Problems debugging g++ code on RS6000 with gdb4.7
Reply-To: tmcconne@sedona.intel.com
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sun, 10 Jan 1993 15:32:38 GMT

In article <9301102237.AA20734@cithe303.cithep.caltech.edu>, you write:
> Hello,
> 
> I've tried this question in comp.unix.aix and gnu.g++.help and have gotten
> no responses, I really hope someone here can help me.
> 
> First off I am running AIX3.2 on an RS6000.
> I am using gcc 2.3.2/libg++ 2.3
> I am using gdb 4.7

  I would _strongly_ recommend moving to gcc-2.3.3. It has a number of bug fixes
over gcc-2.3.2. Also, make sure that libg++-2.3 is rebuilt using gcc-2.3.3. Just
to be complete, I would also rebuild gdb-4.7 with gcc-2.3.3. It is most
difficult to find the problem sometimes when using tools built with different
versions of the compiler.

> 
> I am having problems debugging c++ programs with gdb4.7.
> gdb seems to work OK on small C programs compiled with gcc but I am
> having problems debugging C++ code compiled(-g of course) with g++.
> 
> I should mention that my sys-op says the RS6000 assembly patch(for gcc)  has
> been applied.  Here is an example of what happens when I try to load a
> executable:
> ------------------------------------------------------------------------
> cithe502:wfd > gdb 
> GDB is free software and you are welcome to
> distribute copies of it
>  under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for details.
> GDB 4.7, Copyright 1992 Free Software Foundation, Inc.
> (gdb) file monte
> Reading symbols from monte...GDB Error: `.bf' not found.
> GDB Error: `.bf' not found.
> done.
> (gdb)

  I have seen the "`.bf'" errors on and off with different versions of
gcc/libg++/gdb. With my current setup (gcc-2.3.3, libg++-2.3, gdb-4.7) there are
no errors, and I can debug g++ code just fine.

> 
> -Chris Walter

  Good luck.

    Cheers,

    Tom McConnell

 Tom McConnell          |     Internet: tmcconne@sedona.intel.com
 Intel, Corp. C3-91     |     Phone: (602)-554-8229
 5000 W. Chandler Blvd. | The opinions expressed are my own. No one in 
 Chandler, AZ  85226    | their right mind would claim them.

Newsgroups: gnu.gdb.bug
From: dlong@cse.ucsc.EDU (Dean R. E. Long)
Subject: gdb 4.7 template demangle bug
Organization: University of California, Santa Cruz (CE/CIS Boards)
Distribution: gnu
Date: Sat, 9 Jan 1993 05:21:01 GMT

In libiberty/cplus-dem.c, function demangle_template, the line:

      string_prepend (declp, tname.b);

causes trouble, because tname.b has not been null-terminated.


Newsgroups: gnu.gdb.bug
From: leisner@wrc.xerox.COM ( Marty Leisner)
Subject: seeing return values on sparc?
Reply-To: leisner@eso.mc.xerox.com
Organization: Xerox
Distribution: gnu
Date: Mon, 11 Jan 1993 16:40:30 GMT

How do I see the return value of a function in gdb on sparcs (without adding temporary variables to my code).


BTW -- I'm quite impressed with gdb...;-)

--
marty
leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
Member of the League for Programming Freedom

Newsgroups: gnu.gdb.bug
From: leisner@wrc.xerox.COM ( Marty Leisner)
Subject: automatically configure for screen size
Reply-To: leisner@eso.mc.xerox.com
Organization: Xerox
Distribution: gnu
Date: Sun, 10 Jan 1993 21:33:33 GMT

Would it be possible to configure a mode in gdb to automatically configure on a screen size
(instead of relying on set height num after a window resize...?)

It should be fairly easy...elvis and less do it...

--
marty
leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
Member of the League for Programming Freedom

Newsgroups: gnu.gdb.bug
From: haw30@ras.amdahl.COM (Henry A Worth)
Subject: gdb-4.7 dumps on nil textsection ptr (gcc2.3.3/solaris2/shared object)
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 8 Jan 1993 00:07:14 GMT

   gdb dumped (seg. excep) while trying to attach to a running process
(shared objects in use). The object included a shared object without a
text section which resulted in a nil ptr in the function symbol_add_stub()
in the gdb source file solib.c. gdb-4.7 and the objects were all compiled
with gcc-2.3.3 running under Solaris2.0.


gdb of gdb-4.7's core dump (same error also occurs in earlier gdb's):

     (gdb) core core
     Core was generated by `gdb-4.7 sm'.
     Program terminated with signal 11, Segmentation fault.
     #0  0x67028 in symbol_add_stub (arg=0x2f5208 "") at solib.c:674
     674       so -> objfile = symbol_file_add (so -> so_name, so -> from_tty,

the full statement & function:
 
/* A small stub to get us past the arg-passing pinhole of catch_errors.  */
 
static int
symbol_add_stub (arg)
     char *arg;
{
  register struct so_list *so = (struct so_list *) arg; /* catch_errs bogon */
 
  so -> objfile = symbol_file_add (so -> so_name, so -> from_tty,
                                   (unsigned int) so -> textsection -> addr,
note>>                                            ^^^^^^^^^^^^^^^^^^^^^^^^^^
                                   0, 0, 0);
  return (1);
}

returning to gdb:
     
     (gdb) p so
     $1 = (struct so_list *) 0x2f5208
     (gdb) p *so
     $2 = {next = 0x0, lm = {l_addr = 4014080000, 
         l_name = 0xef7fa2e4<Address 0xef7fa2e4 out of bounds>, 
         l_ld = 0xef434494, 
         l_next = 0xef7fa3dc, l_prev = 0xef7fa254}, lmaddr = 0xef7fa31c, 
       lmend = 4014163092, 
       so_name = {"/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx.so", 

The source file (name changed to protect the guilty) contains a global 
date table and no functions (same error also occurs if it is a .sa  file). 
It was compiled with gcc-2.3.3 with the options: -g -O2 -fno-inline -fpic.

       '\000' <repeats 205 times>}, symbols_loaded = 0 '\000', from_tty = 0 
       '\000', 
       so_bfd = 0x321108, objfile = 0x0, sections = 0x25a908, 
       sections_end = 0x25a928, textsection = 0x0}
note>>                          ^^^^^^^^^^^^^^^^^
     
     (gdb) bt
     #0  0x67028 in symbol_add_stub (arg=0x2f5208 "") at solib.c:674
     #1  0x213c8 in catch_errors (func=0x67008 <_initialize_exec+2120>, 
         args=0x2f5208 "", 
         errstring=0x140140 "Error while reading shared library symbols:\n")
         at main.c:370
     #2  0x67170 in solib_add (arg_string=0x0, from_tty=1, target=0x0)
         at solib.c:728
     #3  0x53904 in attach_command (args=0x18900f "6633", from_tty=1)
         at infcmd.c:1083
     #4  0x226c4 in execute_command (p=0x18900f "6633", from_tty=1) at 
         main.c:931
     #5  0x22928 in command_loop () at main.c:990
     #6  0x22410 in main (argc=2, argv=0xeffff794) at main.c:857


fix(?)/workaround:

Added check of so->textsection, if nil then pass a nil to symbol_file_add() 
for the third argument.
    
 

Newsgroups: gnu.gdb.bug
From: heller@cs.umass.edu (Robert Heller)
Subject: GDB 4.5 Crashes when used with large executables on DECStation 5000s
Organization: COINS, UMass, Amherst
Distribution: gnu
Date: Wed, 6 Jan 1993 19:39:27 GMT

We have encounted a problem with GDB 4.5 on our DECStations.  We have some very large programs, which seem to cause GDB to crash or behave strangely (losing track of the stack or not being able to set brakepoints, etc.).  It seems to behave properly on our Sun4.  Has anyone else had this problem?

		Robert Heller
InterNet:	Heller@CS.UMass.EDU
BIX:		locks.hill.bbs
FidoNet:	1:321/153 (Locks Hill BBS, Wendell, MA)
CompuServe	71450,3432

Newsgroups: gnu.gdb.bug
From: John.Cooper@eng.SUn.COM (John S Cooper)
Subject: gdb fails on Solaris 2.1
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 8 Jan 1993 10:28:28 GMT

Configuration: gdb4.7 built with gcc2.3.3 on Solaris 2.1

Whenever I step over any function in a shared library (in this case,
printf() in libc.so), gdb gives the following segmentation fault:

gdb-4.7/gdb/gdb hello
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.7, Copyright 1992 Free Software Foundation, Inc...
(gdb) b main
Breakpoint 1 at 0x10778: file hello.c, line 8.
(gdb) r
Starting program: /saxon/jsc/hello 

Breakpoint 1, main (argc=1, argv=0xeffff9cc) at hello.c:8
8	    a = 2;
(gdb) n
9	    printf("Hello World\n");
(gdb) n
0x208d0 in __DTOR_END__ ()
(gdb) 
Current function has no line number information.
Single stepping until function exit.

Program received signal 11, Segmentation fault
0xef7d906c in _fp_current_direction ()
(gdb)

The source program is as follows:

#include <stdio.h>

static void bar(int ef);

main(int argc, char **argv)
{
    int a;
    a = 2;
    printf("Hello World\n");
    bar(a);
}

static void
bar(int ef)
{
    printf("%d\n", ef);
}


I posted the same bug a while ago when I had built gdb4.7 with the
SparcWorks compilers, but had no response. Is gdb supported on Solaris
2.x yet?

Thanks for any help,

       --- John.

Newsgroups: gnu.gdb.bug
From: karl@owl.HQ.ILeaf.COM
Subject: (none)
Reply-To: karl@hq.ileaf.com
Organization: GNUs Not Usenet
Distribution: gnu
Date: Tue, 5 Jan 1993 00:50:08 GMT

make distclean in the gdb-4.7/gdb directory tries to remake the TAGS file.
This seems bizarre to me; I expected distclean to only remove things,
not create them!


Newsgroups: gnu.gdb.bug
From: leisner@wrc.xerox.COM ( Marty Leisner)
Subject: setting watchpoints
Reply-To: leisner@eso.mc.xerox.com
Organization: Xerox
Distribution: gnu
Date: Mon, 4 Jan 1993 14:45:53 GMT

I have a simple program:
int i;

main()
{
        for(i = 0; i < 100; i++)
                ;
}

It seems I can't set access I until after the program runs (its using dynamic
libraries) ??

Also, it doesn't seem to stop at my watchpoint...accept when I give it an
interrupt signal (then the program is at the watchpoint):

(gdb) watch i=50
Cannot access memory at address 0x40b8.
(gdb) break main
Breakpoint 1 at 0x229c: file main.c, line 6.
(gdb) run
Starting program: /files1/accounts/leisner/tmp/main 

Breakpoint 1, main () at main.c:6
6               for(i = 0; i < 100; i++)
(gdb) watch i=50
Watchpoint 2: i = 50
(gdb) info watchpoints
Num Type           Disp Enb Address    What
1   breakpoint     keep y   0x0000229c in main at main.c:6
2   watchpoint     keep y   i = 50
(gdb) cont
Continuing.
^C
Program received signal 2, Interrupt
0x22a8 in main () at main.c:6
6               for(i = 0; i < 100; i++)
(gdb) p i
$1 = 50

I only entered a signal after a significant amount of time (maybe 30 seconds?)


--
marty
leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
Member of the League for Programming Freedom

Newsgroups: gnu.gdb.bug
From: grossman@cygnus.com (Stu Grossman)
Subject: Building gcc/gdb on HP/UX with debugging
Organization: GNUs Not Usenet
Distribution: gnu
Date: Mon, 4 Jan 1993 22:43:43 GMT

> 1)Do I need to build gas before building gcc in order to get debugging
> support?

There are really two issues here.  Are you talking about debugging the
compiler, or debugging your gcc compiled programs?  In the former case, you
will definately need to use Utah's pa-gas when building gcc after stage 1.

If you don't use Utah's pa-gas for building gcc, you will have to compile it
WITHOUT the -g option because the native HP assembler doesn't understand the
.stabxxx pseudo-ops.  You will still get a working gcc which is capable of
generating debug output, but you won't be able to debug gcc itself.

In either case, you will need to use Utah's pa-gas in order to use gcc's
debugging info.

> 3)Will gcc-2.3.3 support HP PA with debugging or do I need the version
> of 2.3.1 which is on jaguar (and has been specifically ported for HP
> PA)?  I think building the 2.3.3 release would be better than using
> the 2.1.1 because of bug fixes, etc.

I've been using 2.3.1 from Utah with very few problems.  I haven't tried
2.3.3 yet.

> 3)Once I have gcc-2.x built, do I need to do anything special to build
> pa-gdb-4.6?

Make sure that you install the appropriate patch file from Utah over the
standard GDB-4.6 distribution.  The name is pa-gdb-4.6.tar.Z.  It won't even
compile without that.

> 4)Are there any plans to integrate the utah changes into the
> gas/gcc/gdb standard distributions?

I have been doing a lot of work recently on the PA-GDB port.  It should come
out with release 4.8 of GDB.

			Stu Grossman
			Cygnus Support

Newsgroups: gnu.gdb.bug
From: haider@tao.rice.edu (Haider Abbas Rizvi)
Subject: gdb-4.6 (4.7) bug on rs/6000
Organization: Rice University
Distribution: gnu
Date: Thu, 7 Jan 1993 03:54:02 GMT

I have noticed a bug in the gdb-4.6 when running on a rs/6000 machine. 

When I load a program and run it, it works fine. But if I recompile the
program, and ask gdb to run it again without explicitly reloading it, gdb
gets into a infinite loop; on other machines, gdb determines itself that the
executable is newer and reloads it itself. 

An example session is follows.
----------------------------------------------------------------------------
Current directory is /lido/haider/research/solalg/svd/twops/

(gdb) run
Starting program: /lido/haider/research/solalg/svd/twops/svd.noprof 4 6
matrix size = 4, sweeps = 6
  
****************************************************************************
The program ran and gave some output.
After this I recompiled the program and typed run as below.
****************************************************************************  
  
(gdb) run 4 6
The program being debugged has been started already.
Start it from the beginning? (y or n) y
`/lido/haider/research/solalg/svd/twops/svd.noprof' has changed; re-reading symbols.
`/lido/haider/research/solalg/svd/twops/svd.noprof' has changed; re-reading symbols.
  
****************************************************************************
This line keeps on repeating till I hit C-c C-c
****************************************************************************
(gdb) Quit

----------------------------------------------------------------------------

I have the same code compiled for a sparc, and there it runs correctly.
Has someone else noticed it, has this been discussed. Would someone send a
correction to this if there is one, etc etc.
Please reply by email if you can, I usually don't follow this newsgroup.
Thanks,
--
Haider

Newsgroups: gnu.utils.bug
From: friedman@gnu.ai.mit.edu (Noah Friedman)
Subject: Re: suggestions for getopt*.c in libiberty
Reply-To: friedman@gnu.ai.mit.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 7 Jan 1993 08:16:52 GMT

>The efficiency of getopt is particularly irrelevant - even if
>it made a difference, why do you think the system version is preferable?

   It's probably not, in fact.  GNU getopt allows users to specify options
and arguments in any order, whereas traditional getopt implementations
*require* options first.  

Newsgroups: gnu.utils.bug
From: rogerj@lps.cornell.edu (Roger Jagoda)
Subject: Bug report for screen 3.2b
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 7 Jan 1993 14:09:08 GMT

GNU,
 
HW: DEC VAX running Xinu BSD 4.3
SW: Screen v. 3.2b


-------------------- Configure screen capture --------------------
 
 checking for gcc
 checking for install
 checking for POSIXized ISC
 checking for RiscOS
 checking for Ultrix
 checking for POSIX.1
 checking for BSD job control
 checking for termio or termios
 checking for termcap or terminfo
 checking for shadow.h
 checking for System V
 checking for directory library header
 checking for dirent.h
 checking for closedir return value
 checking for getutent
 checking for libutils
 checking for getloadavg
 checking for mknod declaration
 checking for setpgid declaration
 checking for setreuid
 checking for getttyent
 checking whether bcopy handles overlapping arguments
 checking for vsprintf
 checking for putenv
 checking for pid_t
 checking for sig_t
 checking for long file names
 checking for sys/socket.h
 checking for SVR4 elf library
 checking for SCO crypt and sec libraries
 checking for IRIX sun library
 checking for Xenix
 creating config.status
 creating Makefile
 creating config.h
  
  -------------------- Configure screen capture --------------------
   

The we typed "make all" and got this:

 
 --------------------- make.log --------------------------
  
  cc -c -g  -I. -DETCSCREENRC=\"/usr/local/lib/screenrc\" ./screen.c
  ./screen.h: 528: const redefined
  "./screen.c", line 496: undefined structure
  "./screen.c", line 1101: tv_usec undefined
  "./screen.c", line 1101: member of structure or union required
  "./screen.c", line 1126: tv_sec undefined
  "./screen.c", line 1126: member of structure or union required
  "./screen.c", line 1126: warning: illegal combination of pointer and integer, op =
  "./screen.c", line 1314: undefined structure
  "./screen.c", line 1317: member of structure or union required
  "./screen.c", line 1317: warning: illegal combination of pointer and integer, op =
  "./screen.c", line 1318: tv_sec undefined
  "./screen.c", line 1318: member of structure or union required
  *** Exit 1
   
   Stop.
    
     
 --------------------- make.log --------------------------

 Is there another library we need to add to the loader?

      

Thanks for listening!

--Roger
Roger Jagoda
Cornell University
(607) 255-6115
rogerj@lps.cornell.edu


Newsgroups: gnu.utils.bug
From: boyle@gca.COM (David Boyle)
Subject: GNU tar
Keywords: GNU tar
Organization: GCA Corporation
Distribution: gnu
Date: Thu, 7 Jan 1993 18:18:14 GMT

Using GNU tar version 1.10 on a DECstation/Ultrix machine, tar +help
claims that -c will "create a new archive".  However, if I write the same
archive twice (to tape), the second time goes much faster, as if tar was
checking the existing archive against what is being written an only updating
rather than creating the archive from scratch.  This behavior is what I
would expect from the -u flag, not -the -c flag.  

Is what I described actually happening or am I out to lunch?  If I'm
right, how can I force the archive to be created from scratch?

--
David Boyle                            ...uunet!gca!boyle  or  boyle@gca.com
GCA, a unit of General Signal          (508) 837-3869
Andover, MA  01810

Newsgroups: gnu.utils.bug
From: bothner@cygnus.com
Subject: Re: nm version 2.0 - behaviour of -o on multiple libraries
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 9 Jan 1993 10:21:14 GMT

I sort of agree with your point, but I don't feel like making
changes in the interface without knowing what if anything standards
say on the issue.  Note that SVR4 (and Solaris2) does *not* act as
you request.  Now, we can be better than SVR4, but that requires
sitting down and thinking about what the various options should
do, and what the output should look like.  It also requires research
into standards and existing implementations.  We don't have time for
this, but would welcome a volunteer to do this.

	--Per Bothner
Cygnus Support     bothner@cygnus.com

Newsgroups: gnu.utils.bug
From: mikee@rambo.UUCP (Mike Eggleston)
Subject: autoconf questions
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 6 Jan 1993 17:12:10 GMT

Hello,

I'm probably sending the to the wrong person.  I've got some questions
rather bug reports.

What I'm looking for is instructions on how to have autoconfig
generate the '--with*' instructions within the generates configure
script.  I've been through the autoconfig 1.2 manual, but I can't find
any mention of how to do this.

I agree with and want to follow the suggestions in the standards
document about including '--with-feature' options in the configure
script, but I just haven't figured out how to do it.

Thanks.

Mike Eggleston

American Airlines Decision Technologies
P. O. Box 619616
MD 4462
Dallas/Fort Worth Airport, Texas  75261-9616

(817)931-2287    FAX: (817)967-9763

sun.com!texsun!skywalker!rambo!mikee
or
texsun!skywalker!rambo!mikee@sun.com

Newsgroups: gnu.utils.bug
From: karl@claude.cs.umb.edu (Karl Berry)
Subject: make documentation
Reply-To: karl@cs.umb.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Fri, 8 Jan 1993 05:32:59 GMT

The description of .PRECIOUS in the `Special Targets' node doesn't
mention that dependencies of .PRECIOUS are also not deleted if they are
intermediate files made by a pattern rule.

Newsgroups: gnu.utils.bug