HDTenEightyP/NetNews huggingface dataset:
From: iiitac@PYR.SWAN.AC.UK (Alan Cox)
Newsgroups: gnu.misc.discuss
Subject: EEC and software rights
Date: 2 Sep 92 11:00:49 GMT


The EEC law guarantees you the right to take someones software and
disassemble it for the purpose of making your own application compatible
with that software. it doesn't let you then go off and write books about
what you have found or write a clone - that still needs clean room
techniques. It does mean for example I can dissasemble a DOS driver
and use the info to write a unix driver for the same hardware or find
out how to call the driver myself so that I can use it directly from
an application.

It's actually very rarely an issue, but its a nice protection to have.

[I think thats exactly right, but I haven't been involved in anything
 but the software side for a while (thank Eris)]

Alan
Newsgroups: gnu.misc.discuss,comp.org.eff.talk,comp.unix.bsd,comp.os.mach
From: jkp@cs.HUT.FI (Jyrki Kuoppala)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Reply-To: jkp@cs.HUT.FI (Jyrki Kuoppala)
Organization: Helsinki University of Technology, Finland
Date: Wed, 2 Sep 1992 16:09:37 GMT

>Is there any 'official' source of information about this law suit? It will
>be important to have our facts straight.

Look at prep.ai.mit.edu pub/lpf/att-bsdi, or the gopher server
otax.tky.hut.fi Topics/LPF.

//Jyrki
Newsgroups: gnu.misc.discuss,comp.org.eff.talk,comp.unix.bsd,comp.os.mach,news.groups
From: shirley@fdr.jsc.nasa.gov (Bill Shirley [CSC])
Newsgroups: gnu.misc.discuss
Subject: gdb - sparc - parameters
Keywords: fixed? gdb
Date: 27 Aug 1992 15:27:40 GMT
Organization: Software Technology Branch - NASA/JSC
Originator: shirley@fdr


My version of gdb (4.5) on sparc doesn't print correctly
the parameters that are passed to a function if the 
parameter is larger than an int (32 bit).

This usually occurs when I pass a structure as a parameter.

Is this a bug?
Is it known?
Is it being fixed?  (by some kind soul)

not being able to se values of variables is troublesome while debugging!



-- 
Bill Shirley		|  ``Computer Science is not about computers any 
shirley@fdr.jsc.nasa.gov|	more than astronomy is about telescopes.''
Newsgroups: gnu.misc.discuss
From: rcd@raven.eklektix.com (Dick Dunn)
Subject: Re: Time to boycott Photo CD
Summary: think about consumables
Organization: eklektix - Boulder, Colorado
Date: Tue, 1 Sep 1992 06:58:15 GMT

johnston@me.udel.edu (Bill Johnston) writes:
>My understanding is that the patentable part involves a rewritable
>CD format, and the hardware differences needed...
...
>The photographer may send a couple of rolls of film to be developed 
>and printed as 300 meg to a Photo-CD CD ROM.  Later on, the photographer 
>may send another roll of film along with the CD back to Kodak for another
>few hundred meg of prints.
...
>My bet is that CD media will become cheap enough that rewriting
>will not be seen as a major advantage compared to the hassle of
>trying to convert the marketplace over to a new, incompatible
>hardware standard...

Seems like a bad bet to me.

Think just for a moment what Kodak's current business is.

They deal in "consumables"--stuff you buy and use.  Whether that's good or
bad, they probably have a very good understanding of such markets.

The important part is not that you can take one CD and have them add stuff
to it vs having one CD per roll of film.  It's that you can have fewer CDs
if they can add to it.  You carry around one object vs 3 or 4.  It doesn't
matter whether CD media are cheap.

Organizing the data is a hard problem.  If you have some control over that
at the physical level, you're ahead.
-- 
Dick Dunn    rcd@raven.eklektix.com   -or-   raven!rcd    Boulder, Colorado
				Cats!
Newsgroups: gnu.misc.discuss
From: mcastle@mcs213d.cs.umr.edu (Michael R Castle)
Subject: GNU logo
Date: Sat, 29 Aug 1992 19:51:08 GMT
Organization: University of Missouri - Rolla

Is there anything at all like an official GNU logo??  You know, something to
put on manuals, notebooks, bumper stickers, t-shirts that says "I support the
GNU project, you should too"  type of things.

Would this be a good idea???

just curious,
mrc
Newsgroups: gnu.misc.discuss
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Organization: Novell NPD -- Sandy, UT
Date: Wed, 2 Sep 1992 20:49:09 GMT

In article <37585@sdcc12.ucsd.edu> jclark@sdcc3.ucsd.edu (John Clark) writes:
>Could someone confirm or explain, MCI's use of ATT uplinks and
>downlinks, and how MCI was suppose to make a profit while paying ATT
>for satilite services.

	Simple: MCI didn't have to pay AT&T to use it's long distance lines.

	Almost all third party carriers, except Sprint, use AT&T long distance
lines.  Up until January (of last year?), the breakup settlement imposed by
Judge Green required AT&T to allow use of these facilities *without charge*.

	Sprint, being a subsidiary of GTE, has had access to GTE SpaceNet
prior to geting their fiber optic network installed... under heavy access,
you can still get a circuit through SpaceNet instead of fiber.  In fact,
you can ask for this for modem connections (Sprint's time division and
frequency division multiplexing play hell with most modems).

	The concept of Boycotting AT&T is ridiculous unless one picks a long
distance service that uses a common carrier service that isn't AT&T.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu

---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Xref: sparky gnu.misc.discuss:2843 comp.org.eff.talk:5602 comp.unix.bsd:4952 comp.os.mach:1119 news.groups:17408
From: strnlght@netcom.com (David Sternlight)
Newsgroups: gnu.misc.discuss,comp.org.eff.talk,comp.unix.bsd,comp.os.mach,news.groups
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Date: 1 Sep 92 16:07:27 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)


Here is one more user who is not interested in Bill Vajk imposing his
cause on me. He seems to think the situation is black and white and
he is *****RIGHT*****. This message is to tell him not to be so
certain.
From: khattra@fraser.sfu.ca (Taj Khattra)
Newsgroups: gnu.misc.discuss
Subject: GNU Hurd mailing list ?
Date: 1 Sep 92 20:52:17 GMT
Organization: Simon Fraser University, Burnaby, B.C., Canada

Is there one ? If there is, how does one get onto it ?

--
Taj Khattra
Newsgroups: gnu.misc.discuss,comp.org.eff.talk,comp.unix.bsd,comp.os.mach
From: bryan@uhura1.uucp (Bryan Curnutt)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Reply-To: bryan%uhura1@uunet.uu.net
Organization: Stoner Associates, Inc./DREM Incorporated, Houston Texas
Date: Tue, 1 Sep 1992 09:05:48 GMT

In article <UecUwQO00iUz81B9Qv@andrew.cmu.edu> sean+@andrew.cmu.edu (Sean McLinden) writes:
>
>I suspect that the best way to approach this would be a general posting to
>the entire netnews community informing them, in a succinct manner, what is
>the situation, what are the issues and alternatives, and what is the
>recommended course of action (switching long distance carriers).
>
>[...] It should be
>posted to ALL newsgroups as it affects all of us.

It should NOT be posted to all newsgroups.

First, it does not affect "all of us."  People reading news under
VMS, DOS, MacOS, and other non-UNIX operating systems may not care
about AT&T's legal actions regarding UNIX.

Second, a huge number of newsgroups are clearly inappropriate for
this type of posting.  Readers of rec.music.gdead or sci.aquaria
or even comp.sources.unix really don't need to have "Boycott AT&T"
messages shoved in their faces.

Third, it is extremely bad netiquette to indulge in massive
cross-posting.  It's annoying.  And in some (non-UNIX) sectors of
the net it wastes disk space -- you're talking about >1000 extra
articles if you include the alt.* groups.

If you're confused about any of this, please read the articles
with the following titles in news.announce.newusers:

  Rules for posting to Usenet
  A Primer on How to Work With the Usenet Community
  Emily Postnews Answers Your Questions on Netiquette
-- 
Any opinions above are mine, and do not necessarily reflect the views of SAI.
Bryan Curnutt
bryan%uhura1@uunet.uu.net
Xref: sparky gnu.misc.discuss:2847 comp.org.eff.talk:5606 comp.unix.bsd:4959 comp.os.mach:1123 news.groups:17417
From: wcs@cbnewsh.cb.att.com (Bill Stewart 908-949-0705 erebus.att.com!wcs)
Newsgroups: gnu.misc.discuss,comp.org.eff.talk,comp.unix.bsd,comp.os.mach,news.groups
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Date: 1 Sep 92 19:18:23 GMT
Followup-To: alt.cholesterol
Distribution: usa
Organization: AT&T Bell Labs Random ReOrganization Generator

In article <1992Sep1.180222.20077@blaze.cs.jhu.edu> arromdee@jyusenkyou.cs.jhu.edu (Ken Arromdee) writes:
]In article <1992Sep1.130800.14354@news.acns.nwu.edu> learn@speedy.acns.nwu.edu (William J. Vajk) writes:
]>>First, it does not affect "all of us."  
]>I am once again dismayed at the responses made by supposedly
]>intelligent individuals to affairs which do indeed affect all
]>of us. Perhaps some people simply don't se the connections.

]Anyone can get heart disease.  Should I post articles about cholesterol in
]gnu.misc.discuss because it affects "all of us" and so can go to every
]newsgroup on the net?

Definitely!  Do you know how much cholesterol is in vending-machine junkfood,
and how many Real Hackers eat from vending machines?  It's relevant!
But the article really should have a Followup-To: limiting it to more
appropriate subsets of the newsgroup space.

-- 

				Pray for peace;      Bill
#Bill Stewart 908-949-0705 wcs@anchor.ho.att.com AT&T Bell Labs 4M312 Holmdel NJ
# Any technology distinguishable from magic is not sufficiently advanced ...
From: pous@doorstop.berkeley.edu (Rafael Pous)
Newsgroups: gnu.misc.discuss
Subject: Gnuplot eepic driver with different linestyles?
Date: 1 Sep 1992 01:04:49 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: doorstop.berkeley.edu
Originator: pous@doorstop.berkeley.edu

I am using gnuplot's eepic driver with excellent results and great savings 
in time and memory.  However, all plots come out with the same line 
style.  

Does anybody have a way of getting it to draw different linestyles?

Thanx,
			Rafael Pous (pous@doorstop.berkeley.edu)
Newsgroups: gnu.gdb.bug
From: randys@think.com (Randall Smith)
Subject: Bug/feature request in gdb-4.6.
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 26 Aug 1992 15:14:37 GMT

    In the function define_symbol in gdb-4.6 read the following words:

if (string[0] == CPLUS_MARKER)
    {
      /* Special GNU C++ names.  */
      switch (string[1])
	{
	case 't':
	  SYMBOL_NAME (sym) = obsavestring ("this", strlen ("this"),
					    &objfile -> symbol_obstack);
	  break;
	case 'v': /* $vtbl_ptr_type */
	  /* Was: SYMBOL_NAME (sym) = "vptr"; */
	  goto normal;
	case 'e':
	  SYMBOL_NAME (sym) = obsavestring ("eh_throw", strlen ("eh_throw"),
					    &objfile -> symbol_obstack);
	  break;

	case '_':
	  /* This was an anonymous type that was never fixed up.  */
	  goto normal;

	default:
	  abort ();
	}
    }

    I question the wisdom of calling abort from within define_symbol.
  Specifically, you may be (I am) debugging a mixed C/some other random
  language program and wish to use gdb on it.  That other random language
  may have added extensions to the dbx symbol format that gdb doesn't
  understand, but that do not render gdb useless in debugging that
  language.  I would think that the right thing to do would be to return
  from define_symbol (ie. do nothing for that symbol), possibly printing a
  warning (though this feature should be togglable, or gdb should only tell
  the user about the first three or four instances of it).

							-- Randy

Newsgroups: gnu.gdb.bug
From: mecklen@jensen.cs.utah.edu (Robert Mecklenburg)
Subject: gdb 4.6 cfront-style name demangling problem
Organization: University of Utah CS Dept
Distribution: gnu
Date: Thu, 27 Aug 1992 05:39:41 GMT

gdb 4.6 on SGI IRIX 4.0.1 does not demangle cfront generated local
variables and structure data members correctly.  Here is an example:

junk.c:
struct A {
    int i;
};

main()
{
    A a;
    a.i = 10;
}

46 lotus:~$ gdb junk
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.6, Copyright 1992 Free Software Foundation, Inc...
No symbol "demangle" in current context.
(gdb) b 8
Breakpoint 1 at 0x400210: file junk.c, line 8.
(gdb) run
Starting program: /u/prof/mecklen/junk

Breakpoint 1, main () at junk.c:8
8           a.i = 10;
(gdb) i lo
a::a() = {
  i__1A = 0
}
(gdb) p a
No symbol "a" in current context.
(gdb) p __1a
$1 = {
  i__1A = 0
}
(gdb) p __1a.i
There is no member named i.
(gdb) p __1a.i__1A
$2 = 0
(gdb)

The code generated by cfront for this program is:

/* <<AT&T C++ Translator 2.00 06/30/89>> */
/* < junk.c > */

# 1 "junk.c"
void *__vec_new (void *, int , int , void *);

# 1
void __vec_ct (void *, int , int , void *);

# 1
void __vec_dt (void *, int , int , void *);

# 1
void __vec_delete (void *, int , int , void *, int , int );
typedef int (*__vptp)();
struct __mptr {short d; short i; __vptp f; };

# 1
struct A;struct A {     /* sizeof A == 4 */

# 2
int i__1A ;
};

# 5
int main (void ){ _main();
# 6
{
# 7
struct A __1a ;
__1a . i__1A = 10 ;
}
}
# 9

/* the end */

A bogus fix that I tried is:

diff -r gdb-4.6/gdb/cplus-dem.c gdb-4.6.mashed/gdb/cplus-dem.c
341c344,348
<       if (success && (*mangled != '\0'))
---
>       if (success == 2)
>         {
> 	  string_append( &decl, mangled );
>         }
>       else if (success == 1 && (*mangled != '\0'))
886c893
< 	Returns 1 on success, 0 otherwise.
---
> 	Returns 2 if a cfront local symbol, 1 on other success, 0 otherwise.
918c925,926
<   else if ((scan == *mangled) && (isdigit (scan[2]) || (scan[2] == 'Q')))
---
>   else if (current_demangling_style == gnu_demangling &&
> 	   (scan == *mangled) && (isdigit (scan[2]) || (scan[2] == 'Q')))
923a932,938
>   else if (current_demangling_style == cfront_demangling &&
> 	   (scan == *mangled) && isdigit (scan[2]))
>     {
>       /* A cfront local variable starts with "__<digit>". */
>       *mangled = scan + 3;
>       success = 2;
>     }

Any fixes would be much appreciated.

				Thanks,
				Robert Mecklenburg
				University of Utah

Newsgroups: gnu.gdb.bug
From: muts@fysap.fys.ruu.nl (Peter Mutsaers)
Subject: gdb4.6 + vxworks trap problem
Organization: Rijks Universiteit Utrecht
Distribution: gnu
Date: Thu, 3 Sep 1992 10:45:42 GMT

I configured gdb for a vxworks target. I was under the assumption that
I can now use this gdb for 'target vxworks', but also still for a
local target. However, when I run something, at a breakpoint I get a
signal 5 followed by a signal 7 (emulator trap). This is on a sun3. 

Am I doing something wrong, or is it impossible to do what I want?

Thanks,
--
_________________________________________________________________________
Peter Mutsaers.         |================================================ 
muts@fys.ruu.nl         |        Quod licet bovi, non licet Jovi

Newsgroups: gnu.gdb.bug
From: jimb@occs.cs.oberlin.edu (Jim Blandy)
Subject: Emacs runs slower under GDB 4.6
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 2 Sep 1992 23:18:31 GMT

Regarding my previous message which was summarized by:
>Emacs 18.58 runs *much* slower under GDB 4.6 than under GDB 4.5.  I
>can outtype Emacs running under GDB 4.6, but it runs at a normal speed
>under GDB 4.5.

Perhaps it will be helpful to say that the speed problem only occurs
when using X windows.  If I start Emacs so that it uses the termcap
interface to the outside world, its speed is acceptable.  For example,
suppose your display is named pogo.cs.oberlin.edu:0.0:

pogo$ gdb-4.6 -n xemacs
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.6, Copyright 1992 Free Software Foundation, Inc...
(gdb) run -nw -q
Starting program: /u/src/emacs/19.0/src/xemacs -nw -q

<emacs runs fine>

Program exited normally.
(gdb) run -display pogo.cs.oberlin.edu:0.0 -q
Starting program: /u/src/emacs/19.0/src/xemacs -display pogo.cs.oberlin.edu:0.0 -q

<emacs runs real slow>

Program exited normally.
(gdb)


Newsgroups: gnu.gdb.bug
From: randys@think.com (Randall Smith)
Subject: Bug in gdb-4.6.
Organization: GNUs Not Usenet
Distribution: gnu
Date: Wed, 26 Aug 1992 22:06:34 GMT

    In gdb 4.6 on a sparcstation, I had a problem with the "break" command.
   Specifically, it refused to take an assembly language address for an
  argument.  Following is a transcript of part of the gdb session; the
  first instance of the rror is marked with "<===".

							-- Randy

(gdb) p/x (int) cmcom_pe_get_1W_GET
$1 = 0x356c8
(gdb) x/10i $pc
0x35778 <cmcom_pe_get_1W_GET+176>:	
ld [%l7+0x254], %l7	! 0x33095254 <_mb_cur_max+855179528>
0x3577c <cmcom_pe_get_1W_GET+180>:	tst %l7
0x35780 <cmcom_pe_get_1W_GET+184>:	bne 0x357ec <cmcom_pe_get_1W_GET+292>
0x35784 <cmcom_pe_get_1W_GET+188>:	nop 
0x35788 <cmcom_pe_get_1W_GET+192>:	ld [%g5+0xe00], %i5
0x3578c <cmcom_pe_get_1W_GET+196>:	btst 0x10, %i5
0x35790 <cmcom_pe_get_1W_GET+200>:	be 0x357a0 <cmcom_pe_get_1W_GET+216>
0x35794 <cmcom_pe_get_1W_GET+204>:	nop 
0x35798 <cmcom_pe_get_1W_GET+208>:	b 0x357ac <cmcom_pe_get_1W_GET+228>
0x3579c <cmcom_pe_get_1W_GET+212>:	nop 
(gdb) x/10i $pc - 8
0x35770 <cmcom_pe_get_1W_GET+168>:	
or %o0, 0xbb, %o0	! 0xd80bb <cmtra_constants_base+33135>
0x35774 <cmcom_pe_get_1W_GET+172>:	sethi %hi(0x33095000), %l7
0x35778 <cmcom_pe_get_1W_GET+176>:	
ld [%l7+0x254], %l7	! 0x33095254 <_mb_cur_max+855179528>
0x3577c <cmcom_pe_get_1W_GET+180>:	tst %l7
0x35780 <cmcom_pe_get_1W_GET+184>:	bne 0x357ec <cmcom_pe_get_1W_GET+292>
0x35784 <cmcom_pe_get_1W_GET+188>:	nop 
0x35788 <cmcom_pe_get_1W_GET+192>:	ld [%g5+0xe00], %i5
0x3578c <cmcom_pe_get_1W_GET+196>:	btst 0x10, %i5
0x35790 <cmcom_pe_get_1W_GET+200>:	be 0x357a0 <cmcom_pe_get_1W_GET+216>
0x35794 <cmcom_pe_get_1W_GET+204>:	nop 
(gdb) p $l7
$2 = 856248320
(gdb) p/x $l7
$3 = 0x33095000
(gdb) p/x &cmcom_pe_node_level
$4 = 0xcc254
(gdb) break 0x35774
Function "0x35774" not defined.		<=== Error, I believe
(gdb) help break
Set breakpoint at specified line or function.
Argument may be line number, function name, or "*" and an address.
If line number is specified, break at start of code for that line.
If function is specified, break at start of code for that function.
If an address is specified, break at that exact address.
With no arg, uses current execution address of selected stack frame.
This is useful for breaking on return to a stack frame.

Multiple breakpoints at one place are permitted, and useful if conditional.

Do "help breakpoints" for info on other commands dealing with breakpoints.
(gdb) break (int *()) 0x25774
Function "" not defined.
(gdb) p (int) 0x35774
$5 = 218996
(gdb) break $5
Function "" not defined.
(gdb) break 218996
No line 218996 in file "../src/cmrt_addresses.c".
(gdb) 

Newsgroups: gnu.gdb.bug
From: byron@netapp.COM (Byron Rakitzis)
Subject: not really a bug report; query about possible missing functionality
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 3 Sep 1992 20:12:25 GMT

I'm not quite clear about whether gdb (I have 4.5) is set up in such a
way that it's possible to do cross-debugging with core files. e.g.,
cross-gdb running on a Sun4 with a FooBar executable and a FooBar
core file that's been read across the net.

The way things work right now, a *host-dependent* function gets called
to e.g., scan the core file for register contents. I don't see why
this isn't done through target-dependent code.

Am I missing something? Has someone thought about this problem?

BFD already does the right thing (it reads a FooBar core with the
FooBar routines) so it seems to me that all the fetch_core_registers
functions need to me moved out of the xdep files and into the tdep
files in order to get this to work, but not much more.

Thanks for your time,

Byron Rakitzis.

Newsgroups: gnu.gdb.bug
From: dfavor@logan.tivoli.com (David Favor)
Subject: gdb-4.6 signal problem
Keywords: gdb,signals
Organization: TIVOLI Systems, Inc.
Distribution: gnu
Date: Thu, 3 Sep 1992 13:44:09 GMT

I'm using gdb-4.6 (with no patches applied) under SunOS 4.1.2
for the first time (this off course may be the problem). when
I continue (cont) a program under gdb control then type ^C control
is never returned to gdb. 'info signal 2' says...

(gdb) info signal 2
Signal          Stop    Print   Pass to program Description
SIGINT (2)      Yes     Yes     No              Interrupt

pressing ^C displays '^C', however, gdb continues instead of
returning control to the command line. what am I missing here?

Newsgroups: gnu.gdb.bug
From: pfieland@citron.sw.stratus.com (Peggy Fieland)
Subject: Re: Bug in gdb-4.6.
Organization: Stratus Computer, Software Engineering
Distribution: gnu
Date: Thu, 27 Aug 1992 14:10:06 GMT

When setting breakpoints using an assembly language address it
is necessary to use an asterisk (*) before the address, ie,

citron-tests% gdb misc
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.3, Copyright 1991 Free Software Foundation, Inc...
(gdb) info line 7
Line 7 of "misc.c" starts at pc 0x22ae and ends at 0x22b2.
(gdb) b *0x22ae
Breakpoint 1 at 0x22ae: file misc.c, line 7.
(gdb)


You can find this in the manual in section 5.1.1, setting breakpoints.

Peggy

Newsgroups: gnu.gdb.bug
From: otto@fugue.UUCP (Otto Lind)
Subject: gdb on a NeXT
Organization: GNUs Not Usenet
Distribution: gnu
Date: Thu, 27 Aug 1992 03:42:52 GMT

Currently, gdb 4.6 is not supported on the NeXT. Is there any chance that it
will be supported? If not, what version will be distributed with the 3.0
NeXT OS when it's released?

Thanks in advance,

Otto

-- 
Otto Lind                            Sybase, Inc.
otto@sybase.com                      6475 Christie Ave Emeryville, CA 94608
{pacbell,pyramid,sun}!sybase!otto    (510) 596-3691

Newsgroups: gnu.gdb.bug
From: robertb@cs.washington.edu (Robert Bedichek)
Subject: Re: User-defined commands - adding arguments, control structures
Keywords: user-defined commands, arguments, control structures
Organization: Computer Science & Engineering, U. of Washington, Seattle
Distribution: gnu
Date: Wed, 26 Aug 1992 03:17:36 GMT

In article <helgaas.714761661@convex.convex.com> helgaas@convex.com (Bjorn Helgaas) writes:
>It would be very useful if user-defined commands could take arguments
>and include loops and conditionals.  I may end up adding some of this
>functionality myself, but it looks like quite a lot of work, so I'm
>wondering whether anyone else is already working on it.
>
>Bjorn (helgaas@convex.com)

Tektronix did it to version 3.2 of gdb.  They added both arguments
and control mechanisms (if and while).  While you might not end up
using much of their code, you could take a look at it.  It is
in ~ftp/pub/g88.tar.Z on cs.washington.edu.  Look in the file
programmer.c.

	Robert Bedichek   robertb@cs.washington.edu