start tracking user visible changes
This commit is contained in:
parent
1c5d60496e
commit
21cc14d850
2 changed files with 13 additions and 0 deletions
|
@ -1,5 +1,8 @@
|
|||
Wed Jun 16 16:08:18 1993 K. Richard Pixley (rich@sendai.cygnus.com)
|
||||
|
||||
* NEWS: tracking user visible changes starting with
|
||||
vxworks-timeout.
|
||||
|
||||
* remote-vx.c (_initialize_vx): rename user settable option from
|
||||
rpcTimeout to vxworks-timeout.
|
||||
|
||||
|
|
10
gdb/NEWS
10
gdb/NEWS
|
@ -1,6 +1,16 @@
|
|||
What has changed since GDB-3.5?
|
||||
(Organized release by release)
|
||||
|
||||
*** Changes in GDB-???:
|
||||
|
||||
* User visible changes:
|
||||
|
||||
All vxworks based targets now support a user settable option, called
|
||||
vxworks-timeout. This option represents the number of seconds gdb
|
||||
should wait for responses to rpc's. You might want to use this if
|
||||
your vxworks target is, perhaps, a slow software simulator or happens
|
||||
to be on the far side of a thin network line.
|
||||
|
||||
*** Changes in GDB-4.9:
|
||||
|
||||
* Testsuite
|
||||
|
|
Loading…
Reference in a new issue