OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [gdb-5.3/] [gdb/] [NEWS] - Blame information for rev 1765

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 1181 sfurman
                What has changed in GDB?
2
             (Organized release by release)
3
 
4
*** Changes in GDB 5.3:
5
 
6
* GNU/Linux shared library multi-threaded performance improved.
7
 
8
When debugging a multi-threaded application on GNU/Linux, GDB now uses
9
`/proc', in preference to `ptrace' for memory reads.  This may result
10
in an improvement in the start-up time of multi-threaded, shared
11
library applications when run under GDB.  One GDB user writes: ``loads
12
shared libs like mad''.
13
 
14
* ``gdbserver'' now supports multi-threaded applications on some targets
15
 
16
Support for debugging multi-threaded applications which use
17
the GNU/Linux LinuxThreads package has been added for
18
arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
19
powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
20
 
21
* GDB now supports C/C++ preprocessor macros.
22
 
23
GDB now expands preprocessor macro invocations in C/C++ expressions,
24
and provides various commands for showing macro definitions and how
25
they expand.
26
 
27
The new command `macro expand EXPRESSION' expands any macro
28
invocations in expression, and shows the result.
29
 
30
The new command `show macro MACRO-NAME' shows the definition of the
31
macro named MACRO-NAME, and where it was defined.
32
 
33
Most compilers don't include information about macros in the debugging
34
information by default.  In GCC 3.1, for example, you need to compile
35
your program with the options `-gdwarf-2 -g3'.  If the macro
36
information is present in the executable, GDB will read it.
37
 
38
* Multi-arched targets.
39
 
40
DEC Alpha (partial)                             alpha*-*-*
41
DEC VAX (partial)                               vax-*-*
42
NEC V850                                        v850-*-*
43
National Semiconductor NS32000 (partial)        ns32k-*-*
44
Motorola 68000 (partial)                        m68k-*-*
45
Motorola MCORE                                  mcore-*-*
46
 
47
* New targets.
48
 
49
Fujitsu FRV architecture added by Red Hat       frv*-*-*
50
 
51
 
52
* New native configurations
53
 
54
Alpha NetBSD                                    alpha*-*-netbsd*
55
SH NetBSD                                       sh*-*-netbsdelf*
56
MIPS NetBSD                                     mips*-*-netbsd*
57
UltraSPARC NetBSD                               sparc64-*-netbsd*
58
 
59
* OBSOLETE configurations and files
60
 
61
Configurations that have been declared obsolete in this release have
62
been commented out.  Unless there is activity to revive these
63
configurations, the next release of GDB will have their sources
64
permanently REMOVED.
65
 
66
Mitsubishi D30V                                 d30v-*-*
67
OS/9000                                         i[34]86-*-os9k
68
IBM AIX PS/2                                    i[3456]86-*-aix
69
Fujitsu FR30                                    fr30-*-elf*
70
Motorola Delta 88000 running Sys V              m88k-motorola-sysv  or  delta88
71
Argonaut Risc Chip (ARC)                        arc-*-*
72
i386 running Mach 3.0                           i[3456]86-*-mach3*
73
i386 running Mach                               i[3456]86-*-mach*
74
i386 running OSF/1                              i[3456]86-*osf1mk*
75
HP/Apollo 68k Family                            m68*-apollo*-sysv*,
76
                                                m68*-apollo*-bsd*,
77
                                                m68*-hp-bsd*, m68*-hp-hpux*
78
I960 with MON960                                i960-*-coff
79
 
80
* OBSOLETE languages
81
 
82
CHILL, a Pascal like language used by telecommunications companies.
83
 
84
* REMOVED configurations and files
85
 
86
AMD 29k family via UDI                          a29k-amd-udi, udi29k
87
A29K VxWorks                                    a29k-*-vxworks
88
AMD 29000 embedded, using EBMON                 a29k-none-none
89
AMD 29000 embedded with COFF                    a29k-none-coff
90
AMD 29000 embedded with a.out                   a29k-none-aout
91
 
92
testsuite/gdb.hp/gdb.threads-hp/                directory
93
 
94
* New command "set max-user-call-depth "
95
 
96
This command allows the user to limit the call depth of user-defined
97
commands.  The default is 1024.
98
 
99
* Changes in FreeBSD/i386 native debugging.
100
 
101
Support for the "generate-core-file" has been added.
102
 
103
* New commands "dump", "append", and "restore".
104
 
105
These commands allow data to be copied from target memory
106
to a bfd-format or binary file (dump and append), and back
107
from a file into memory (restore).
108
 
109
* Improved "next/step" support on multi-processor Alpha Tru64.
110
 
111
The previous single-step mechanism could cause unpredictable problems,
112
including the random appearance of SIGSEGV or SIGTRAP signals. The use
113
of a software single-step mechanism prevents this.
114
 
115
*** Changes in GDB 5.2.1:
116
 
117
* New targets.
118
 
119
Atmel AVR                                       avr*-*-*
120
 
121
* Bug fixes
122
 
123
gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
124
mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
125
Fix, by Joel Brobecker imported from mainline.
126
 
127
gdb/439: gdb/291: On some ELF object files, gdb was reporting:
128
dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
129
Fix, by Fred Fish, imported from mainline.
130
 
131
Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
132
Surprisingly enough, it works now.
133
By Michal Ludvig, imported from mainline.
134
 
135
i386 hardware watchpoint support:
136
avoid misses on second run for some targets.
137
By Pierre Muller, imported from mainline.
138
 
139
*** Changes in GDB 5.2:
140
 
141
* New command "set trust-readonly-sections on[off]".
142
 
143
This command is a hint that tells gdb that read-only sections
144
really are read-only (ie. that their contents will not change).
145
In this mode, gdb will go to the object file rather than the
146
target to read memory from read-only sections (such as ".text").
147
This can be a significant performance improvement on some
148
(notably embedded) targets.
149
 
150
* New command "generate-core-file" (or "gcore").
151
 
152
This new gdb command allows the user to drop a core file of the child
153
process state at any time.  So far it's been implemented only for
154
GNU/Linux and Solaris, but should be relatively easily ported to other
155
hosts.  Argument is core file name (defaults to core.).
156
 
157
* New command line option
158
 
159
GDB now accepts --pid or -p followed by a process id.
160
 
161
* Change in command line behavior -- corefiles vs. process ids.
162
 
163
There is a subtle behavior in the way in which GDB handles
164
command line arguments.  The first non-flag argument is always
165
a program to debug, but the second non-flag argument may either
166
be a corefile or a process id.  Previously, GDB would attempt to
167
open the second argument as a corefile, and if that failed, would
168
issue a superfluous error message and then attempt to attach it as
169
a process.  Now, if the second argument begins with a non-digit,
170
it will be treated as a corefile.  If it begins with a digit,
171
GDB will attempt to attach it as a process, and if no such process
172
is found, will then attempt to open it as a corefile.
173
 
174
* Changes in ARM configurations.
175
 
176
Multi-arch support is enabled for all ARM configurations.  The ARM/NetBSD
177
configuration is fully multi-arch.
178
 
179
* New native configurations
180
 
181
ARM NetBSD                                      arm*-*-netbsd*
182
x86 OpenBSD                                     i[3456]86-*-openbsd*
183
AMD x86-64 running GNU/Linux                    x86_64-*-linux-*
184
Sparc64 running FreeBSD                         sparc64-*-freebsd*
185
 
186
* New targets
187
 
188
Sanyo XStormy16                                 xstormy16-elf
189
 
190
* OBSOLETE configurations and files
191
 
192
Configurations that have been declared obsolete in this release have
193
been commented out.  Unless there is activity to revive these
194
configurations, the next release of GDB will have their sources
195
permanently REMOVED.
196
 
197
AMD 29k family via UDI                          a29k-amd-udi, udi29k
198
A29K VxWorks                                    a29k-*-vxworks
199
AMD 29000 embedded, using EBMON                 a29k-none-none
200
AMD 29000 embedded with COFF                    a29k-none-coff
201
AMD 29000 embedded with a.out                   a29k-none-aout
202
 
203
testsuite/gdb.hp/gdb.threads-hp/                directory
204
 
205
* REMOVED configurations and files
206
 
207
TI TMS320C80                                    tic80-*-*
208
WDC 65816                                       w65-*-*
209
PowerPC Solaris                                 powerpcle-*-solaris*
210
PowerPC Windows NT                              powerpcle-*-cygwin32
211
PowerPC Netware                                 powerpc-*-netware*
212
Harris/CXUX m88k                                m88*-harris-cxux*
213
Most ns32k hosts and targets                    ns32k-*-mach3* ns32k-umax-*
214
                                                ns32k-utek-sysv* ns32k-utek-*
215
SunOS 4.0.Xi on i386                            i[3456]86-*-sunos*
216
Ultracomputer (29K) running Sym1                a29k-nyu-sym1 a29k-*-kern*
217
Sony NEWS (68K) running NEWSOS 3.x              m68*-sony-sysv news
218
ISI Optimum V (3.05) under 4.3bsd.              m68*-isi-*
219
Apple Macintosh (MPW) host and target           N/A host, powerpc-*-macos*
220
 
221
* Changes to command line processing
222
 
223
The new `--args' feature can be used to specify command-line arguments
224
for the inferior from gdb's command line.
225
 
226
* Changes to key bindings
227
 
228
There is a new `operate-and-get-next' function bound to `C-o'.
229
 
230
*** Changes in GDB 5.1.1
231
 
232
Fix compile problem on DJGPP.
233
 
234
Fix a problem with floating-point registers on the i386 being
235
corrupted.
236
 
237
Fix to stop GDB crashing on .debug_str debug info.
238
 
239
Numerous documentation fixes.
240
 
241
Numerous testsuite fixes.
242
 
243
*** Changes in GDB 5.1:
244
 
245
* New native configurations
246
 
247
Alpha FreeBSD                                   alpha*-*-freebsd*
248
x86 FreeBSD 3.x and 4.x                         i[3456]86*-freebsd[34]*
249
MIPS GNU/Linux                                  mips*-*-linux*
250
MIPS SGI Irix 6.x                               mips*-sgi-irix6*
251
ia64 AIX                                        ia64-*-aix*
252
s390 and s390x GNU/Linux                        {s390,s390x}-*-linux*
253
 
254
* New targets
255
 
256
Motorola 68HC11 and 68HC12                      m68hc11-elf
257
CRIS                                            cris-axis
258
UltraSparc running GNU/Linux                    sparc64-*-linux*
259
 
260
* OBSOLETE configurations and files
261
 
262
x86 FreeBSD before 2.2                          i[3456]86*-freebsd{1,2.[01]}*,
263
Harris/CXUX m88k                                m88*-harris-cxux*
264
Most ns32k hosts and targets                    ns32k-*-mach3* ns32k-umax-*
265
                                                ns32k-utek-sysv* ns32k-utek-*
266
TI TMS320C80                                    tic80-*-*
267
WDC 65816                                       w65-*-*
268
Ultracomputer (29K) running Sym1                a29k-nyu-sym1 a29k-*-kern*
269
PowerPC Solaris                                 powerpcle-*-solaris*
270
PowerPC Windows NT                              powerpcle-*-cygwin32
271
PowerPC Netware                                 powerpc-*-netware*
272
SunOS 4.0.Xi on i386                            i[3456]86-*-sunos*
273
Sony NEWS (68K) running NEWSOS 3.x              m68*-sony-sysv news
274
ISI Optimum V (3.05) under 4.3bsd.              m68*-isi-*
275
Apple Macintosh (MPW) host                      N/A
276
 
277
stuff.c (Program to stuff files into a specially prepared space in kdb)
278
kdb-start.c (Main loop for the standalone kernel debugger)
279
 
280
Configurations that have been declared obsolete in this release have
281
been commented out.  Unless there is activity to revive these
282
configurations, the next release of GDB will have their sources
283
permanently REMOVED.
284
 
285
* REMOVED configurations and files
286
 
287
Altos 3068                                      m68*-altos-*
288
Convex                                          c1-*-*, c2-*-*
289
Pyramid                                         pyramid-*-*
290
ARM RISCix                                      arm-*-* (as host)
291
Tahoe                                           tahoe-*-*
292
ser-ocd.c                                       *-*-*
293
 
294
* GDB has been converted to ISO C.
295
 
296
GDB's source code has been converted to ISO C.  In particular, the
297
sources are fully protoized, and rely on standard headers being
298
present.
299
 
300
* Other news:
301
 
302
* "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
303
 
304
* The MI enabled by default.
305
 
306
The new machine oriented interface (MI) introduced in GDB 5.0 has been
307
revised and enabled by default.  Packages which use GDB as a debugging
308
engine behind a UI or another front end are encouraged to switch to
309
using the GDB/MI interface, instead of the old annotations interface
310
which is now deprecated.
311
 
312
* Support for debugging Pascal programs.
313
 
314
GDB now includes support for debugging Pascal programs.  The following
315
main features are supported:
316
 
317
    - Pascal-specific data types such as sets;
318
 
319
    - automatic recognition of Pascal sources based on file-name
320
      extension;
321
 
322
    - Pascal-style display of data types, variables, and functions;
323
 
324
    - a Pascal expression parser.
325
 
326
However, some important features are not yet supported.
327
 
328
    - Pascal string operations are not supported at all;
329
 
330
    - there are some problems with boolean types;
331
 
332
    - Pascal type hexadecimal constants are not supported
333
      because they conflict with the internal variables format;
334
 
335
    - support for Pascal objects and classes is not full yet;
336
 
337
    - unlike Pascal, GDB is case-sensitive for symbol names.
338
 
339
* Changes in completion.
340
 
341
Commands such as `shell', `run' and `set args', which pass arguments
342
to inferior programs, now complete on file names, similar to what
343
users expect at the shell prompt.
344
 
345
Commands which accept locations, such as `disassemble', `print',
346
`breakpoint', `until', etc. now complete on filenames as well as
347
program symbols.  Thus, if you type "break foob TAB", and the source
348
files linked into the programs include `foobar.c', that file name will
349
be one of the candidates for completion.  However, file names are not
350
considered for completion after you typed a colon that delimits a file
351
name from a name of a function in that file, as in "break foo.c:bar".
352
 
353
`set demangle-style' completes on available demangling styles.
354
 
355
* New platform-independent commands:
356
 
357
It is now possible to define a post-hook for a command as well as a
358
hook that runs before the command.  For more details, see the
359
documentation of `hookpost' in the GDB manual.
360
 
361
* Changes in GNU/Linux native debugging.
362
 
363
Support for debugging multi-threaded programs has been completely
364
revised for all platforms except m68k and sparc.  You can now debug as
365
many threads as your system allows you to have.
366
 
367
Attach/detach is supported for multi-threaded programs.
368
 
369
Support for SSE registers was added for x86.  This doesn't work for
370
multi-threaded programs though.
371
 
372
* Changes in MIPS configurations.
373
 
374
Multi-arch support is enabled for all MIPS configurations.
375
 
376
GDB can now be built as native debugger on SGI Irix 6.x systems for
377
debugging n32 executables.  (Debugging 64-bit executables is not yet
378
supported.)
379
 
380
* Unified support for hardware watchpoints in all x86 configurations.
381
 
382
Most (if not all) native x86 configurations support hardware-assisted
383
breakpoints and watchpoints in a unified manner.  This support
384
implements debug register sharing between watchpoints, which allows to
385
put a virtually infinite number of watchpoints on the same address,
386
and also supports watching regions up to 16 bytes with several debug
387
registers.
388
 
389
The new maintenance command `maintenance show-debug-regs' toggles
390
debugging print-outs in functions that insert, remove, and test
391
watchpoints and hardware breakpoints.
392
 
393
* Changes in the DJGPP native configuration.
394
 
395
New command ``info dos sysinfo'' displays assorted information about
396
the CPU, OS, memory, and DPMI server.
397
 
398
New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
399
display information about segment descriptors stored in GDT, LDT, and
400
IDT.
401
 
402
New commands ``info dos pde'' and ``info dos pte'' display entries
403
from Page Directory and Page Tables (for now works with CWSDPMI only).
404
New command ``info dos address-pte'' displays the Page Table entry for
405
a given linear address.
406
 
407
GDB can now pass command lines longer than 126 characters to the
408
program being debugged (requires an update to the libdbg.a library
409
which is part of the DJGPP development kit).
410
 
411
DWARF2 debug info is now supported.
412
 
413
It is now possible to `step' and `next' through calls to `longjmp'.
414
 
415
* Changes in documentation.
416
 
417
All GDB documentation was converted to GFDL, the GNU Free
418
Documentation License.
419
 
420
Tracepoints-related commands are now fully documented in the GDB
421
manual.
422
 
423
TUI, the Text-mode User Interface, is now documented in the manual.
424
 
425
Tracepoints-related commands are now fully documented in the GDB
426
manual.
427
 
428
The "GDB Internals" manual now has an index.  It also includes
429
documentation of `ui_out' functions, GDB coding standards, x86
430
hardware watchpoints, and memory region attributes.
431
 
432
* GDB's version number moved to ``version.in''
433
 
434
The Makefile variable VERSION has been replaced by the file
435
``version.in''.  People creating GDB distributions should update the
436
contents of this file.
437
 
438
* gdba.el deleted
439
 
440
GUD support is now a standard part of the EMACS distribution.
441
 
442
*** Changes in GDB 5.0:
443
 
444
* Improved support for debugging FP programs on x86 targets
445
 
446
Unified and much-improved support for debugging floating-point
447
programs on all x86 targets.  In particular, ``info float'' now
448
displays the FP registers in the same format on all x86 targets, with
449
greater level of detail.
450
 
451
* Improvements and bugfixes in hardware-assisted watchpoints
452
 
453
It is now possible to watch array elements, struct members, and
454
bitfields with hardware-assisted watchpoints.  Data-read watchpoints
455
on x86 targets no longer erroneously trigger when the address is
456
written.
457
 
458
* Improvements in the native DJGPP version of GDB
459
 
460
The distribution now includes all the scripts and auxiliary files
461
necessary to build the native DJGPP version on MS-DOS/MS-Windows
462
machines ``out of the box''.
463
 
464
The DJGPP version can now debug programs that use signals.  It is
465
possible to catch signals that happened in the debuggee, deliver
466
signals to it, interrupt it with Ctrl-C, etc.  (Previously, a signal
467
would kill the program being debugged.)  Programs that hook hardware
468
interrupts (keyboard, timer, etc.) can also be debugged.
469
 
470
It is now possible to debug DJGPP programs that redirect their
471
standard handles or switch them to raw (as opposed to cooked) mode, or
472
even close them.  The command ``run < foo > bar'' works as expected,
473
and ``info terminal'' reports useful information about the debuggee's
474
terminal, including raw/cooked mode, redirection, etc.
475
 
476
The DJGPP version now uses termios functions for console I/O, which
477
enables debugging graphics programs.  Interrupting GDB with Ctrl-C
478
also works.
479
 
480
DOS-style file names with drive letters are now fully supported by
481
GDB.
482
 
483
It is now possible to debug DJGPP programs that switch their working
484
directory.  It is also possible to rerun the debuggee any number of
485
times without restarting GDB; thus, you can use the same setup,
486
breakpoints, etc. for many debugging sessions.
487
 
488
* New native configurations
489
 
490
ARM GNU/Linux                                   arm*-*-linux*
491
PowerPC GNU/Linux                               powerpc-*-linux*
492
 
493
* New targets
494
 
495
Motorola MCore                                  mcore-*-*
496
x86 VxWorks                                     i[3456]86-*-vxworks*
497
PowerPC VxWorks                                 powerpc-*-vxworks*
498
TI TMS320C80                                    tic80-*-*
499
 
500
* OBSOLETE configurations
501
 
502
Altos 3068                                      m68*-altos-*
503
Convex                                          c1-*-*, c2-*-*
504
Pyramid                                         pyramid-*-*
505
ARM RISCix                                      arm-*-* (as host)
506
Tahoe                                           tahoe-*-*
507
 
508
Configurations that have been declared obsolete will be commented out,
509
but the code will be left in place.  If there is no activity to revive
510
these configurations before the next release of GDB, the sources will
511
be permanently REMOVED.
512
 
513
* Gould support removed
514
 
515
Support for the Gould PowerNode and NP1 has been removed.
516
 
517
* New features for SVR4
518
 
519
On SVR4 native platforms (such as Solaris), if you attach to a process
520
without first loading a symbol file, GDB will now attempt to locate and
521
load symbols from the running process's executable file.
522
 
523
* Many C++ enhancements
524
 
525
C++ support has been greatly improved. Overload resolution now works properly
526
in almost all cases. RTTI support is on the way.
527
 
528
* Remote targets can connect to a sub-program
529
 
530
A popen(3) style serial-device has been added.  This device starts a
531
sub-process (such as a stand-alone simulator) and then communicates
532
with that.  The sub-program to run is specified using the syntax
533
``| '' vis:
534
 
535
        (gdb) set remotedebug 1
536
        (gdb) target extended-remote |mn10300-elf-sim program-args
537
 
538
* MIPS 64 remote protocol
539
 
540
A long standing bug in the mips64 remote protocol where by GDB
541
expected certain 32 bit registers (ex SR) to be transfered as 32
542
instead of 64 bits has been fixed.
543
 
544
The command ``set remote-mips64-transfers-32bit-regs on'' has been
545
added to provide backward compatibility with older versions of GDB.
546
 
547
* ``set remotebinarydownload'' replaced by ``set remote X-packet''
548
 
549
The command ``set remotebinarydownload'' command has been replaced by
550
``set remote X-packet''.  Other commands in ``set remote'' family
551
include ``set remote P-packet''.
552
 
553
* Breakpoint commands accept ranges.
554
 
555
The breakpoint commands ``enable'', ``disable'', and ``delete'' now
556
accept a range of breakpoints, e.g. ``5-7''.  The tracepoint command
557
``tracepoint passcount'' also accepts a range of tracepoints.
558
 
559
* ``apropos'' command added.
560
 
561
The ``apropos'' command searches through command names and
562
documentation strings, printing out matches, making it much easier to
563
try to find a command that does what you are looking for.
564
 
565
* New MI interface
566
 
567
A new machine oriented interface (MI) has been added to GDB.  This
568
interface is designed for debug environments running GDB as a separate
569
process.  This is part of the long term libGDB project.  See the
570
"GDB/MI" chapter of the GDB manual for further information.  It can be
571
enabled by configuring with:
572
 
573
        .../configure --enable-gdbmi
574
 
575
*** Changes in GDB-4.18:
576
 
577
* New native configurations
578
 
579
HP-UX 10.20                                     hppa*-*-hpux10.20
580
HP-UX 11.x                                      hppa*-*-hpux11.0*
581
M68K GNU/Linux                                  m68*-*-linux*
582
 
583
* New targets
584
 
585
Fujitsu FR30                                    fr30-*-elf*
586
Intel StrongARM                                 strongarm-*-*
587
Mitsubishi D30V                                 d30v-*-*
588
 
589
* OBSOLETE configurations
590
 
591
Gould PowerNode, NP1                            np1-*-*, pn-*-*
592
 
593
Configurations that have been declared obsolete will be commented out,
594
but the code will be left in place.  If there is no activity to revive
595
these configurations before the next release of GDB, the sources will
596
be permanently REMOVED.
597
 
598
* ANSI/ISO C
599
 
600
As a compatibility experiment, GDB's source files buildsym.h and
601
buildsym.c have been converted to pure standard C, no longer
602
containing any K&R compatibility code.  We believe that all systems in
603
use today either come with a standard C compiler, or have a GCC port
604
available.  If this is not true, please report the affected
605
configuration to bug-gdb@gnu.org immediately.  See the README file for
606
information about getting a standard C compiler if you don't have one
607
already.
608
 
609
* Readline 2.2
610
 
611
GDB now uses readline 2.2.
612
 
613
* set extension-language
614
 
615
You can now control the mapping between filename extensions and source
616
languages by using the `set extension-language' command.  For instance,
617
you can ask GDB to treat .c files as C++ by saying
618
        set extension-language .c c++
619
The command `info extensions' lists all of the recognized extensions
620
and their associated languages.
621
 
622
* Setting processor type for PowerPC and RS/6000
623
 
624
When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
625
you can use the `set processor' command to specify what variant of the
626
PowerPC family you are debugging.  The command
627
 
628
        set processor NAME
629
 
630
sets the PowerPC/RS6000 variant to NAME.  GDB knows about the
631
following PowerPC and RS6000 variants:
632
 
633
  ppc-uisa  PowerPC UISA - a PPC processor as viewed by user-level code
634
  rs6000    IBM RS6000 ("POWER") architecture, user-level view
635
  403       IBM PowerPC 403
636
  403GC     IBM PowerPC 403GC
637
  505       Motorola PowerPC 505
638
  860       Motorola PowerPC 860 or 850
639
  601       Motorola PowerPC 601
640
  602       Motorola PowerPC 602
641
  603       Motorola/IBM PowerPC 603 or 603e
642
  604       Motorola PowerPC 604 or 604e
643
  750       Motorola/IBM PowerPC 750 or 750
644
 
645
At the moment, this command just tells GDB what to name the
646
special-purpose processor registers.  Since almost all the affected
647
registers are inaccessible to user-level programs, this command is
648
only useful for remote debugging in its present form.
649
 
650
* HP-UX support
651
 
652
Thanks to a major code donation from Hewlett-Packard, GDB now has much
653
more extensive support for HP-UX.  Added features include shared
654
library support, kernel threads and hardware watchpoints for 11.00,
655
support for HP's ANSI C and C++ compilers, and a compatibility mode
656
for xdb and dbx commands.
657
 
658
* Catchpoints
659
 
660
HP's donation includes the new concept of catchpoints, which is a
661
generalization of the old catch command.  On HP-UX, it is now possible
662
to catch exec, fork, and vfork, as well as library loading.
663
 
664
This means that the existing catch command has changed; its first
665
argument now specifies the type of catch to be set up.  See the
666
output of "help catch" for a list of catchpoint types.
667
 
668
* Debugging across forks
669
 
670
On HP-UX, you can choose which process to debug when a fork() happens
671
in the inferior.
672
 
673
* TUI
674
 
675
HP has donated a curses-based terminal user interface (TUI).  To get
676
it, build with --enable-tui.  Although this can be enabled for any
677
configuration, at present it only works for native HP debugging.
678
 
679
* GDB remote protocol additions
680
 
681
A new protocol packet 'X' that writes binary data is now available.
682
Default behavior is to try 'X', then drop back to 'M' if the stub
683
fails to respond.  The settable variable `remotebinarydownload'
684
allows explicit control over the use of 'X'.
685
 
686
For 64-bit targets, the memory packets ('M' and 'm') can now contain a
687
full 64-bit address.  The command
688
 
689
        set remoteaddresssize 32
690
 
691
can be used to revert to the old behaviour.  For existing remote stubs
692
the change should not be noticed, as the additional address information
693
will be discarded.
694
 
695
In order to assist in debugging stubs, you may use the maintenance
696
command `packet' to send any text string to the stub.  For instance,
697
 
698
        maint packet heythere
699
 
700
sends the packet "$heythere#".  Note that it is very easy to
701
disrupt a debugging session by sending the wrong packet at the wrong
702
time.
703
 
704
The compare-sections command allows you to compare section data on the
705
target to what is in the executable file without uploading or
706
downloading, by comparing CRC checksums.
707
 
708
* Tracing can collect general expressions
709
 
710
You may now collect general expressions at tracepoints.  This requires
711
further additions to the target-side stub; see tracepoint.c and
712
doc/agentexpr.texi for further details.
713
 
714
* mask-address variable for Mips
715
 
716
For Mips targets, you may control the zeroing of the upper 32 bits of
717
a 64-bit address by entering `set mask-address on'.  This is mainly
718
of interest to users of embedded R4xxx and R5xxx processors.
719
 
720
* Higher serial baud rates
721
 
722
GDB's serial code now allows you to specify baud rates 57600, 115200,
723
230400, and 460800 baud.  (Note that your host system may not be able
724
to achieve all of these rates.)
725
 
726
* i960 simulator
727
 
728
The i960 configuration now includes an initial implementation of a
729
builtin simulator, contributed by Jim Wilson.
730
 
731
 
732
*** Changes in GDB-4.17:
733
 
734
* New native configurations
735
 
736
Alpha GNU/Linux                                 alpha*-*-linux*
737
Unixware 2.x                                    i[3456]86-unixware2*
738
Irix 6.x                                        mips*-sgi-irix6*
739
PowerPC GNU/Linux                               powerpc-*-linux*
740
PowerPC Solaris                                 powerpcle-*-solaris*
741
Sparc GNU/Linux                                 sparc-*-linux*
742
Motorola sysV68 R3V7.1                          m68k-motorola-sysv
743
 
744
* New targets
745
 
746
Argonaut Risc Chip (ARC)                        arc-*-*
747
Hitachi H8/300S                                 h8300*-*-*
748
Matsushita MN10200 w/simulator                  mn10200-*-*
749
Matsushita MN10300 w/simulator                  mn10300-*-*
750
MIPS NEC VR4100                                 mips64*vr4100*{,el}-*-elf*
751
MIPS NEC VR5000                                 mips64*vr5000*{,el}-*-elf*
752
MIPS Toshiba TX39                               mips64*tx39*{,el}-*-elf*
753
Mitsubishi D10V w/simulator                     d10v-*-*
754
Mitsubishi M32R/D w/simulator                   m32r-*-elf*
755
Tsqware Sparclet                                sparclet-*-*
756
NEC V850 w/simulator                            v850-*-*
757
 
758
* New debugging protocols
759
 
760
ARM with RDI protocol                           arm*-*-*
761
M68K with dBUG monitor                          m68*-*-{aout,coff,elf}
762
DDB and LSI variants of PMON protocol           mips*-*-*
763
PowerPC with DINK32 monitor                     powerpc{,le}-*-eabi
764
PowerPC with SDS protocol                       powerpc{,le}-*-eabi
765
Macraigor OCD (Wiggler) devices                 powerpc{,le}-*-eabi
766
 
767
* DWARF 2
768
 
769
All configurations can now understand and use the DWARF 2 debugging
770
format.  The choice is automatic, if the symbol file contains DWARF 2
771
information.
772
 
773
* Java frontend
774
 
775
GDB now includes basic Java language support.  This support is
776
only useful with Java compilers that produce native machine code.
777
 
778
* solib-absolute-prefix and solib-search-path
779
 
780
For SunOS and SVR4 shared libraries, you may now set the prefix for
781
loading absolute shared library symbol files, and the search path for
782
locating non-absolute shared library symbol files.
783
 
784
* Live range splitting
785
 
786
GDB can now effectively debug code for which GCC has performed live
787
range splitting as part of its optimization.  See gdb/doc/LRS for
788
more details on the expected format of the stabs information.
789
 
790
* Hurd support
791
 
792
GDB's support for the GNU Hurd, including thread debugging, has been
793
updated to work with current versions of the Hurd.
794
 
795
* ARM Thumb support
796
 
797
GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
798
instruction set.  ARM GDB automatically detects when Thumb
799
instructions are in use, and adjusts disassembly and backtracing
800
accordingly.
801
 
802
* MIPS16 support
803
 
804
GDB's MIPS target configurations now handle the MIP16 16-bit
805
instruction set.
806
 
807
* Overlay support
808
 
809
GDB now includes support for overlays; if an executable has been
810
linked such that multiple sections are based at the same address, GDB
811
will decide which section to use for symbolic info.  You can choose to
812
control the decision manually, using overlay commands, or implement
813
additional target-side support and use "overlay load-target" to bring
814
in the overlay mapping.  Do "help overlay" for more detail.
815
 
816
* info symbol
817
 
818
The command "info symbol 
" displays information about
819
the symbol at the specified address.
820
 
821
* Trace support
822
 
823
The standard remote protocol now includes an extension that allows
824
asynchronous collection and display of trace data.  This requires
825
extensive support in the target-side debugging stub.  Tracing mode
826
includes a new interaction mode in GDB and new commands: see the
827
file tracepoint.c for more details.
828
 
829
* MIPS simulator
830
 
831
Configurations for embedded MIPS now include a simulator contributed
832
by Cygnus Solutions.  The simulator supports the instruction sets
833
of most MIPS variants.
834
 
835
* Sparc simulator
836
 
837
Sparc configurations may now include the ERC32 simulator contributed
838
by the European Space Agency.  The simulator is not built into
839
Sparc targets by default; configure with --enable-sim to include it.
840
 
841
* set architecture
842
 
843
For target configurations that may include multiple variants of a
844
basic architecture (such as MIPS and SH), you may now set the
845
architecture explicitly.  "set arch" sets, "info arch" lists
846
the possible architectures.
847
 
848
*** Changes in GDB-4.16:
849
 
850
* New native configurations
851
 
852
Windows 95, x86 Windows NT                      i[345]86-*-cygwin32
853
M68K NetBSD                                     m68k-*-netbsd*
854
PowerPC AIX 4.x                                 powerpc-*-aix*
855
PowerPC MacOS                                   powerpc-*-macos*
856
PowerPC Windows NT                              powerpcle-*-cygwin32
857
RS/6000 AIX 4.x                                 rs6000-*-aix4*
858
 
859
* New targets
860
 
861
ARM with RDP protocol                           arm-*-*
862
I960 with MON960                                i960-*-coff
863
MIPS VxWorks                                    mips*-*-vxworks*
864
MIPS VR4300 with PMON                           mips64*vr4300{,el}-*-elf*
865
PowerPC with PPCBUG monitor                     powerpc{,le}-*-eabi*
866
Hitachi SH3                                     sh-*-*
867
Matra Sparclet                                  sparclet-*-*
868
 
869
* PowerPC simulator
870
 
871
The powerpc-eabi configuration now includes the PSIM simulator,
872
contributed by Andrew Cagney, with assistance from Mike Meissner.
873
PSIM is a very elaborate model of the PowerPC, including not only
874
basic instruction set execution, but also details of execution unit
875
performance and I/O hardware.  See sim/ppc/README for more details.
876
 
877
* Solaris 2.5
878
 
879
GDB now works with Solaris 2.5.
880
 
881
* Windows 95/NT native
882
 
883
GDB will now work as a native debugger on Windows 95 and Windows NT.
884
To build it from source, you must use the "gnu-win32" environment,
885
which uses a DLL to emulate enough of Unix to run the GNU tools.
886
Further information, binaries, and sources are available at
887
ftp.cygnus.com, under pub/gnu-win32.
888
 
889
* dont-repeat command
890
 
891
If a user-defined command includes the command `dont-repeat', then the
892
command will not be repeated if the user just types return.  This is
893
useful if the command is time-consuming to run, so that accidental
894
extra keystrokes don't run the same command many times.
895
 
896
* Send break instead of ^C
897
 
898
The standard remote protocol now includes an option to send a break
899
rather than a ^C to the target in order to interrupt it.  By default,
900
GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
901
 
902
* Remote protocol timeout
903
 
904
The standard remote protocol includes a new variable `remotetimeout'
905
that allows you to set the number of seconds before GDB gives up trying
906
to read from the target.  The default value is 2.
907
 
908
* Automatic tracking of dynamic object loading (HPUX and Solaris only)
909
 
910
By default GDB will automatically keep track of objects as they are
911
loaded and unloaded by the dynamic linker.  By using the command `set
912
stop-on-solib-events 1' you can arrange for GDB to stop the inferior
913
when shared library events occur, thus allowing you to set breakpoints
914
in shared libraries which are explicitly loaded by the inferior.
915
 
916
Note this feature does not work on hpux8.  On hpux9 you must link
917
/usr/lib/end.o into your program.  This feature should work
918
automatically on hpux10.
919
 
920
* Irix 5.x hardware watchpoint support
921
 
922
Irix 5 configurations now support the use of hardware watchpoints.
923
 
924
* Mips protocol "SYN garbage limit"
925
 
926
When debugging a Mips target using the `target mips' protocol, you
927
may set the number of characters that GDB will ignore by setting
928
the `syn-garbage-limit'.  A value of -1 means that GDB will ignore
929
every character.  The default value is 1050.
930
 
931
* Recording and replaying remote debug sessions
932
 
933
If you set `remotelogfile' to the name of a file, gdb will write to it
934
a recording of a remote debug session.  This recording may then be
935
replayed back to gdb using "gdbreplay".  See gdbserver/README for
936
details.  This is useful when you have a problem with GDB while doing
937
remote debugging; you can make a recording of the session and send it
938
to someone else, who can then recreate the problem.
939
 
940
* Speedups for remote debugging
941
 
942
GDB includes speedups for downloading and stepping MIPS systems using
943
the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
944
and more efficient S-record downloading.
945
 
946
* Memory use reductions and statistics collection
947
 
948
GDB now uses less memory and reports statistics about memory usage.
949
Try the `maint print statistics' command, for example.
950
 
951
*** Changes in GDB-4.15:
952
 
953
* Psymtabs for XCOFF
954
 
955
The symbol reader for AIX GDB now uses partial symbol tables.  This
956
can greatly improve startup time, especially for large executables.
957
 
958
* Remote targets use caching
959
 
960
Remote targets now use a data cache to speed up communication with the
961
remote side.  The data cache could lead to incorrect results because
962
it doesn't know about volatile variables, thus making it impossible to
963
debug targets which use memory mapped I/O devices. `set remotecache
964
off' turns the the data cache off.
965
 
966
* Remote targets may have threads
967
 
968
The standard remote protocol now includes support for multiple threads
969
in the target system, using new protocol commands 'H' and 'T'.  See
970
gdb/remote.c for details.
971
 
972
* NetROM support
973
 
974
If GDB is configured with `--enable-netrom', then it will include
975
support for the NetROM ROM emulator from XLNT Designs.  The NetROM
976
acts as though it is a bank of ROM on the target board, but you can
977
write into it over the network.  GDB's support consists only of
978
support for fast loading into the emulated ROM; to debug, you must use
979
another protocol, such as standard remote protocol.  The usual
980
sequence is something like
981
 
982
        target nrom 
983
        load 
984
        target remote :1235
985
 
986
* Macintosh host
987
 
988
GDB now includes support for the Apple Macintosh, as a host only.  It
989
may be run as either an MPW tool or as a standalone application, and
990
it can debug through the serial port.  All the usual GDB commands are
991
available, but to the target command, you must supply "serial" as the
992
device type instead of "/dev/ttyXX".  See mpw-README in the main
993
directory for more information on how to build.  The MPW configuration
994
scripts */mpw-config.in support only a few targets, and only the
995
mips-idt-ecoff target has been tested.
996
 
997
* Autoconf
998
 
999
GDB configuration now uses autoconf.  This is not user-visible,
1000
but does simplify configuration and building.
1001
 
1002
* hpux10
1003
 
1004
GDB now supports hpux10.
1005
 
1006
*** Changes in GDB-4.14:
1007
 
1008
* New native configurations
1009
 
1010
x86 FreeBSD                                     i[345]86-*-freebsd
1011
x86 NetBSD                                      i[345]86-*-netbsd
1012
NS32k NetBSD                                    ns32k-*-netbsd
1013
Sparc NetBSD                                    sparc-*-netbsd
1014
 
1015
* New targets
1016
 
1017
A29K VxWorks                                    a29k-*-vxworks
1018
HP PA PRO embedded (WinBond W89K & Oki OP50N)   hppa*-*-pro*
1019
CPU32 EST-300 emulator                          m68*-*-est*
1020
PowerPC ELF                                     powerpc-*-elf
1021
WDC 65816                                       w65-*-*
1022
 
1023
* Alpha OSF/1 support for procfs
1024
 
1025
GDB now supports procfs under OSF/1-2.x and higher, which makes it
1026
possible to attach to running processes.  As the mounting of the /proc
1027
filesystem is optional on the Alpha, GDB automatically determines
1028
the availability of /proc during startup.  This can lead to problems
1029
if /proc is unmounted after GDB has been started.
1030
 
1031
* Arguments to user-defined commands
1032
 
1033
User commands may accept up to 10 arguments separated by whitespace.
1034
Arguments are accessed within the user command via $arg0..$arg9.  A
1035
trivial example:
1036
define adder
1037
  print $arg0 + $arg1 + $arg2
1038
 
1039
To execute the command use:
1040
adder 1 2 3
1041
 
1042
Defines the command "adder" which prints the sum of its three arguments.
1043
Note the arguments are text substitutions, so they may reference variables,
1044
use complex expressions, or even perform inferior function calls.
1045
 
1046
* New `if' and `while' commands
1047
 
1048
This makes it possible to write more sophisticated user-defined
1049
commands.  Both commands take a single argument, which is the
1050
expression to evaluate, and must be followed by the commands to
1051
execute, one per line, if the expression is nonzero, the list being
1052
terminated by the word `end'.  The `if' command list may include an
1053
`else' word, which causes the following commands to be executed only
1054
if the expression is zero.
1055
 
1056
* Fortran source language mode
1057
 
1058
GDB now includes partial support for Fortran 77.  It will recognize
1059
Fortran programs and can evaluate a subset of Fortran expressions, but
1060
variables and functions may not be handled correctly.  GDB will work
1061
with G77, but does not yet know much about symbols emitted by other
1062
Fortran compilers.
1063
 
1064
* Better HPUX support
1065
 
1066
Most debugging facilities now work on dynamic executables for HPPAs
1067
running hpux9 or later.  You can attach to running dynamically linked
1068
processes, but by default the dynamic libraries will be read-only, so
1069
for instance you won't be able to put breakpoints in them.  To change
1070
that behavior do the following before running the program:
1071
 
1072
        adb -w a.out
1073
        __dld_flags?W 0x5
1074
        control-d
1075
 
1076
This will cause the libraries to be mapped private and read-write.
1077
To revert to the normal behavior, do this:
1078
 
1079
        adb -w a.out
1080
        __dld_flags?W 0x4
1081
        control-d
1082
 
1083
You cannot set breakpoints or examine data in the library until after
1084
the library is loaded if the function/data symbols do not have
1085
external linkage.
1086
 
1087
GDB can now also read debug symbols produced by the HP C compiler on
1088
HPPAs (sorry, no C++, Fortran or 68k support).
1089
 
1090
* Target byte order now dynamically selectable
1091
 
1092
You can choose which byte order to use with a target system, via the
1093
commands "set endian big" and "set endian little", and you can see the
1094
current setting by using "show endian".  You can also give the command
1095
"set endian auto", in which case GDB will use the byte order
1096
associated with the executable.  Currently, only embedded MIPS
1097
configurations support dynamic selection of target byte order.
1098
 
1099
* New DOS host serial code
1100
 
1101
This version uses DPMI interrupts to handle buffered I/O, so you
1102
no longer need to run asynctsr when debugging boards connected to
1103
a PC's serial port.
1104
 
1105
*** Changes in GDB-4.13:
1106
 
1107
* New "complete" command
1108
 
1109
This lists all the possible completions for the rest of the line, if it
1110
were to be given as a command itself.  This is intended for use by emacs.
1111
 
1112
* Trailing space optional in prompt
1113
 
1114
"set prompt" no longer adds a space for you after the prompt you set.  This
1115
allows you to set a prompt which ends in a space or one that does not.
1116
 
1117
* Breakpoint hit counts
1118
 
1119
"info break" now displays a count of the number of times the breakpoint
1120
has been hit.  This is especially useful in conjunction with "ignore"; you
1121
can ignore a large number of breakpoint hits, look at the breakpoint info
1122
to see how many times the breakpoint was hit, then run again, ignoring one
1123
less than that number, and this will get you quickly to the last hit of
1124
that breakpoint.
1125
 
1126
* Ability to stop printing at NULL character
1127
 
1128
"set print null-stop" will cause GDB to stop printing the characters of
1129
an array when the first NULL is encountered.  This is useful when large
1130
arrays actually contain only short strings.
1131
 
1132
* Shared library breakpoints
1133
 
1134
In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1135
breakpoints in shared libraries before the executable is run.
1136
 
1137
* Hardware watchpoints
1138
 
1139
There is a new hardware breakpoint for the watch command for sparclite
1140
targets.  See gdb/sparclite/hw_breakpoint.note.
1141
 
1142
Hardware watchpoints are also now supported under GNU/Linux.
1143
 
1144
* Annotations
1145
 
1146
Annotations have been added.  These are for use with graphical interfaces,
1147
and are still experimental.  Currently only gdba.el uses these.
1148
 
1149
* Improved Irix 5 support
1150
 
1151
GDB now works properly with Irix 5.2.
1152
 
1153
* Improved HPPA support
1154
 
1155
GDB now works properly with the latest GCC and GAS.
1156
 
1157
* New native configurations
1158
 
1159
Sequent PTX4                            i[34]86-sequent-ptx4
1160
HPPA running OSF/1                      hppa*-*-osf*
1161
Atari TT running SVR4                   m68*-*-sysv4*
1162
RS/6000 LynxOS                          rs6000-*-lynxos*
1163
 
1164
* New targets
1165
 
1166
OS/9000                                 i[34]86-*-os9k
1167
MIPS R4000                              mips64*{,el}-*-{ecoff,elf}
1168
Sparc64                                 sparc64-*-*
1169
 
1170
* Hitachi SH7000 and E7000-PC ICE support
1171
 
1172
There is now support for communicating with the Hitachi E7000-PC ICE.
1173
This is available automatically when GDB is configured for the SH.
1174
 
1175
* Fixes
1176
 
1177
As usual, a variety of small fixes and improvements, both generic
1178
and configuration-specific.  See the ChangeLog for more detail.
1179
 
1180
*** Changes in GDB-4.12:
1181
 
1182
* Irix 5 is now supported
1183
 
1184
* HPPA support
1185
 
1186
GDB-4.12 on the HPPA has a number of changes which make it unable
1187
to debug the output from the currently released versions of GCC and
1188
GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36).  Until the next major release
1189
of GCC and GAS, versions of these tools designed to work with GDB-4.12
1190
can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1191
 
1192
 
1193
*** Changes in GDB-4.11:
1194
 
1195
* User visible changes:
1196
 
1197
* Remote Debugging
1198
 
1199
The "set remotedebug" option is now consistent between the mips remote
1200
target, remote targets using the gdb-specific protocol, UDI (AMD's
1201
debug protocol for the 29k) and the 88k bug monitor.  It is now an
1202
integer specifying a debug level (normally 0 or 1, but 2 means more
1203
debugging info for the mips target).
1204
 
1205
* DEC Alpha native support
1206
 
1207
GDB now works on the DEC Alpha.  GCC 2.4.5 does not produce usable
1208
debug info, but GDB works fairly well with the DEC compiler and should
1209
work with a future GCC release.  See the README file for a few
1210
Alpha-specific notes.
1211
 
1212
* Preliminary thread implementation
1213
 
1214
GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1215
 
1216
* LynxOS native and target support for 386
1217
 
1218
This release has been hosted on LynxOS 2.2, and also can be configured
1219
to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1220
for details).
1221
 
1222
* Improvements in C++ mangling/demangling.
1223
 
1224
This release has much better g++ debugging, specifically in name
1225
mangling/demangling, virtual function calls, print virtual table,
1226
call methods, ...etc.
1227
 
1228
*** Changes in GDB-4.10:
1229
 
1230
 * User visible changes:
1231
 
1232
Remote debugging using the GDB-specific (`target remote') protocol now
1233
supports the `load' command.  This is only useful if you have some
1234
other way of getting the stub to the target system, and you can put it
1235
somewhere in memory where it won't get clobbered by the download.
1236
 
1237
Filename completion now works.
1238
 
1239
When run under emacs mode, the "info line" command now causes the
1240
arrow to point to the line specified.  Also, "info line" prints
1241
addresses in symbolic form (as well as hex).
1242
 
1243
All vxworks based targets now support a user settable option, called
1244
vxworks-timeout.  This option represents the number of seconds gdb
1245
should wait for responses to rpc's.  You might want to use this if
1246
your vxworks target is, perhaps, a slow software simulator or happens
1247
to be on the far side of a thin network line.
1248
 
1249
 * DEC alpha support
1250
 
1251
This release contains support for using a DEC alpha as a GDB host for
1252
cross debugging.  Native alpha debugging is not supported yet.
1253
 
1254
 
1255
*** Changes in GDB-4.9:
1256
 
1257
 * Testsuite
1258
 
1259
This is the first GDB release which is accompanied by a matching testsuite.
1260
The testsuite requires installation of dejagnu, which should be available
1261
via ftp from most sites that carry GNU software.
1262
 
1263
 * C++ demangling
1264
 
1265
'Cfront' style demangling has had its name changed to 'ARM' style, to
1266
emphasize that it was written from the specifications in the C++ Annotated
1267
Reference Manual, not necessarily to be compatible with AT&T cfront.  Despite
1268
disclaimers, it still generated too much confusion with users attempting to
1269
use gdb with AT&T cfront.
1270
 
1271
 * Simulators
1272
 
1273
GDB now uses a standard remote interface to a simulator library.
1274
So far, the library contains simulators for the Zilog Z8001/2, the
1275
Hitachi H8/300, H8/500 and Super-H.
1276
 
1277
 * New targets supported
1278
 
1279
H8/300 simulator                        h8300-hitachi-hms or h8300hms
1280
H8/500 simulator                        h8500-hitachi-hms or h8500hms
1281
SH simulator                            sh-hitachi-hms    or sh
1282
Z8000 simulator                         z8k-zilog-none    or z8ksim
1283
IDT MIPS board over serial line         mips-idt-ecoff
1284
 
1285
Cross-debugging to GO32 targets is supported.  It requires a custom
1286
version of the i386-stub.c module which is integrated with the
1287
GO32 memory extender.
1288
 
1289
 * New remote protocols
1290
 
1291
MIPS remote debugging protocol.
1292
 
1293
 * New source languages supported
1294
 
1295
This version includes preliminary support for Chill, a Pascal like language
1296
used by telecommunications companies.  Chill support is also being integrated
1297
into the GNU compiler, but we don't know when it will be publically available.
1298
 
1299
 
1300
*** Changes in GDB-4.8:
1301
 
1302
 * HP Precision Architecture supported
1303
 
1304
GDB now supports HP PA-RISC machines running HPUX.  A preliminary
1305
version of this support was available as a set of patches from the
1306
University of Utah.  GDB does not support debugging of programs
1307
compiled with the HP compiler, because HP will not document their file
1308
format.  Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1309
(as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1310
 
1311
Many problems in the preliminary version have been fixed.
1312
 
1313
 * Faster and better demangling
1314
 
1315
We have improved template demangling and fixed numerous bugs in the GNU style
1316
demangler.  It can now handle type modifiers such as `static' or `const'.  Wide
1317
character types (wchar_t) are now supported.  Demangling of each symbol is now
1318
only done once, and is cached when the symbol table for a file is read in.
1319
This results in a small increase in memory usage for C programs, a moderate
1320
increase in memory usage for C++ programs, and a fantastic speedup in
1321
symbol lookups.
1322
 
1323
`Cfront' style demangling still doesn't work with AT&T cfront.  It was written
1324
from the specifications in the Annotated Reference Manual, which AT&T's
1325
compiler does not actually implement.
1326
 
1327
 * G++ multiple inheritance compiler problem
1328
 
1329
In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1330
inheritance lattices was reworked to properly discover ambiguities.  We
1331
recently found an example which causes this new algorithm to fail in a
1332
very subtle way, producing bad debug information for those classes.
1333
The file 'gcc.patch' (in this directory) can be applied to gcc to
1334
circumvent the problem.  A future GCC release will contain a complete
1335
fix.
1336
 
1337
The previous G++ debug info problem (mentioned below for the gdb-4.7
1338
release) is fixed in gcc version 2.3.2.
1339
 
1340
 * Improved configure script
1341
 
1342
The `configure' script will now attempt to guess your system type if
1343
you don't supply a host system type.  The old scheme of supplying a
1344
host system triplet is preferable over using this.  All the magic is
1345
done in the new `config.guess' script.  Examine it for details.
1346
 
1347
We have also brought our configure script much more in line with the FSF's
1348
version.  It now supports the --with-xxx options.  In particular,
1349
`--with-minimal-bfd' can be used to make the GDB binary image smaller.
1350
The resulting GDB will not be able to read arbitrary object file formats --
1351
only the format ``expected'' to be used on the configured target system.
1352
We hope to make this the default in a future release.
1353
 
1354
 * Documentation improvements
1355
 
1356
There's new internal documentation on how to modify GDB, and how to
1357
produce clean changes to the code.  We implore people to read it
1358
before submitting changes.
1359
 
1360
The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1361
M4 macros.  The new texinfo.tex is provided in this release.  Pre-built
1362
`info' files are also provided.  To build `info' files from scratch,
1363
you will need the latest `makeinfo' release, which will be available in
1364
a future texinfo-X.Y release.
1365
 
1366
*NOTE*  The new texinfo.tex can cause old versions of TeX to hang.
1367
We're not sure exactly which versions have this problem, but it has
1368
been seen in 3.0.  We highly recommend upgrading to TeX version 3.141
1369
or better.  If that isn't possible, there is a patch in
1370
`texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1371
around this problem.
1372
 
1373
 * New features
1374
 
1375
GDB now supports array constants that can be used in expressions typed in by
1376
the user.  The syntax is `{element, element, ...}'.  Ie: you can now type
1377
`print {1, 2, 3}', and it will build up an array in memory malloc'd in
1378
the target program.
1379
 
1380
The new directory `gdb/sparclite' contains a program that demonstrates
1381
how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1382
 
1383
 * New native hosts supported
1384
 
1385
HP/PA-RISC under HPUX using GNU tools   hppa1.1-hp-hpux
1386
386 CPUs running SCO Unix 3.2v4         i386-unknown-sco3.2v4
1387
 
1388
 * New targets supported
1389
 
1390
AMD 29k family via UDI                  a29k-amd-udi  or  udi29k
1391
 
1392
 * New file formats supported
1393
 
1394
BFD now supports reading HP/PA-RISC executables (SOM file format?),
1395
HPUX core files, and SCO 3.2v2 core files.
1396
 
1397
 * Major bug fixes
1398
 
1399
Attaching to processes now works again; thanks for the many bug reports.
1400
 
1401
We have also stomped on a bunch of core dumps caused by
1402
printf_filtered("%s") problems.
1403
 
1404
We eliminated a copyright problem on the rpc and ptrace header files
1405
for VxWorks, which was discovered at the last minute during the 4.7
1406
release.  You should now be able to build a VxWorks GDB.
1407
 
1408
You can now interrupt gdb while an attached process is running.  This
1409
will cause the attached process to stop, and give control back to GDB.
1410
 
1411
We fixed problems caused by using too many file descriptors
1412
for reading symbols from object files and libraries.  This was
1413
especially a problem for programs that used many (~100) shared
1414
libraries.
1415
 
1416
The `step' command now only enters a subroutine if there is line number
1417
information for the subroutine.  Otherwise it acts like the `next'
1418
command.  Previously, `step' would enter subroutines if there was
1419
any debugging information about the routine.  This avoids problems
1420
when using `cc -g1' on MIPS machines.
1421
 
1422
 * Internal improvements
1423
 
1424
GDB's internal interfaces have been improved to make it easier to support
1425
debugging of multiple languages in the future.
1426
 
1427
GDB now uses a common structure for symbol information internally.
1428
Minimal symbols (derived from linkage symbols in object files), partial
1429
symbols (from a quick scan of debug information), and full symbols
1430
contain a common subset of information, making it easier to write
1431
shared code that handles any of them.
1432
 
1433
 * New command line options
1434
 
1435
We now accept --silent as an alias for --quiet.
1436
 
1437
 * Mmalloc licensing
1438
 
1439
The memory-mapped-malloc library is now licensed under the GNU Library
1440
General Public License.
1441
 
1442
*** Changes in GDB-4.7:
1443
 
1444
 * Host/native/target split
1445
 
1446
GDB has had some major internal surgery to untangle the support for
1447
hosts and remote targets.  Now, when you configure GDB for a remote
1448
target, it will no longer load in all of the support for debugging
1449
local programs on the host.  When fully completed and tested, this will
1450
ensure that arbitrary host/target combinations are possible.
1451
 
1452
The primary conceptual shift is to separate the non-portable code in
1453
GDB into three categories.  Host specific code is required any time GDB
1454
is compiled on that host, regardless of the target.  Target specific
1455
code relates to the peculiarities of the target, but can be compiled on
1456
any host.  Native specific code is everything else:  it can only be
1457
built when the host and target are the same system.  Child process
1458
handling and core file support are two common `native' examples.
1459
 
1460
GDB's use of /proc for controlling Unix child processes is now cleaner.
1461
It has been split out into a single module under the `target_ops' vector,
1462
plus two native-dependent functions for each system that uses /proc.
1463
 
1464
 * New hosts supported
1465
 
1466
HP/Apollo 68k (under the BSD domain)    m68k-apollo-bsd  or  apollo68bsd
1467
386 CPUs running various BSD ports      i386-unknown-bsd  or  386bsd
1468
386 CPUs running SCO Unix               i386-unknown-scosysv322  or  i386sco
1469
 
1470
 * New targets supported
1471
 
1472
Fujitsu SPARClite                       sparclite-fujitsu-none  or  sparclite
1473
68030 and CPU32                         m68030-*-*, m68332-*-*
1474
 
1475
 * New native hosts supported
1476
 
1477
386 CPUs running various BSD ports      i386-unknown-bsd  or  386bsd
1478
    (386bsd is not well tested yet)
1479
386 CPUs running SCO Unix               i386-unknown-scosysv322  or  sco
1480
 
1481
 * New file formats supported
1482
 
1483
BFD now supports COFF files for the Zilog Z8000 microprocessor.  It
1484
supports reading of `a.out.adobe' object files, which are an a.out
1485
format extended with minimal information about multiple sections.
1486
 
1487
 * New commands
1488
 
1489
`show copying' is the same as the old `info copying'.
1490
`show warranty' is the same as `info warrantee'.
1491
These were renamed for consistency.  The old commands continue to work.
1492
 
1493
`info handle' is a new alias for `info signals'.
1494
 
1495
You can now define pre-command hooks, which attach arbitrary command
1496
scripts to any command.  The commands in the hook will be executed
1497
prior to the user's command.  You can also create a hook which will be
1498
executed whenever the program stops.  See gdb.texinfo.
1499
 
1500
 * C++ improvements
1501
 
1502
We now deal with Cfront style name mangling, and can even extract type
1503
info from mangled symbols.  GDB can automatically figure out which
1504
symbol mangling style your C++ compiler uses.
1505
 
1506
Calling of methods and virtual functions has been improved as well.
1507
 
1508
 * Major bug fixes
1509
 
1510
The crash that occured when debugging Sun Ansi-C compiled binaries is
1511
fixed.  This was due to mishandling of the extra N_SO stabs output
1512
by the compiler.
1513
 
1514
We also finally got Ultrix 4.2 running in house, and fixed core file
1515
support, with help from a dozen people on the net.
1516
 
1517
John M. Farrell discovered that the reason that single-stepping was so
1518
slow on all of the Mips based platforms (primarily SGI and DEC) was
1519
that we were trying to demangle and lookup a symbol used for internal
1520
purposes on every instruction that was being stepped through.  Changing
1521
the name of that symbol so that it couldn't be mistaken for a C++
1522
mangled symbol sped things up a great deal.
1523
 
1524
Rich Pixley sped up symbol lookups in general by getting much smarter
1525
about when C++ symbol mangling is necessary.  This should make symbol
1526
completion (TAB on the command line) much faster.  It's not as fast as
1527
we'd like, but it's significantly faster than gdb-4.6.
1528
 
1529
 * AMD 29k support
1530
 
1531
A new user controllable variable 'call_scratch_address' can
1532
specify the location of a scratch area to be used when GDB
1533
calls a function in the target.  This is necessary because the
1534
usual method of putting the scratch area on the stack does not work
1535
in systems that have separate instruction and data spaces.
1536
 
1537
We integrated changes to support the 29k UDI (Universal Debugger
1538
Interface), but discovered at the last minute that we didn't have all
1539
of the appropriate copyright paperwork.  We are working with AMD to
1540
resolve this, and hope to have it available soon.
1541
 
1542
 * Remote interfaces
1543
 
1544
We have sped up the remote serial line protocol, especially for targets
1545
with lots of registers.  It now supports a new `expedited status' ('T')
1546
message which can be used in place of the existing 'S' status message.
1547
This allows the remote stub to send only the registers that GDB
1548
needs to make a quick decision about single-stepping or conditional
1549
breakpoints, eliminating the need to fetch the entire register set for
1550
each instruction being stepped through.
1551
 
1552
The GDB remote serial protocol now implements a write-through cache for
1553
registers, only re-reading the registers if the target has run.
1554
 
1555
There is also a new remote serial stub for SPARC processors.  You can
1556
find it in gdb-4.7/gdb/sparc-stub.c.  This was written to support the
1557
Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1558
processor with a serial port.
1559
 
1560
 * Configuration
1561
 
1562
Configure.in files have become much easier to read and modify.  A new
1563
`table driven' format makes it more obvious what configurations are
1564
supported, and what files each one uses.
1565
 
1566
 * Library changes
1567
 
1568
There is a new opcodes library which will eventually contain all of the
1569
disassembly routines and opcode tables.  At present, it only contains
1570
Sparc and Z8000 routines.  This will allow the assembler, debugger, and
1571
disassembler (binutils/objdump) to share these routines.
1572
 
1573
The libiberty library is now copylefted under the GNU Library General
1574
Public License.  This allows more liberal use, and was done so libg++
1575
can use it.  This makes no difference to GDB, since the Library License
1576
grants all the rights from the General Public License.
1577
 
1578
 * Documentation
1579
 
1580
The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1581
reference to the stabs symbol info used by the debugger.  It is (as far
1582
as we know) the only published document on this fascinating topic.  We
1583
encourage you to read it, compare it to the stabs information on your
1584
system, and send improvements on the document in general (to
1585
bug-gdb@prep.ai.mit.edu).
1586
 
1587
And, of course, many bugs have been fixed.
1588
 
1589
 
1590
*** Changes in GDB-4.6:
1591
 
1592
 * Better support for C++ function names
1593
 
1594
GDB now accepts as input the "demangled form" of C++ overloaded function
1595
names and member function names, and can do command completion on such names
1596
(using TAB, TAB-TAB, and ESC-?).  The names have to be quoted with a pair of
1597
single quotes.  Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1598
Make use of command completion, it is your friend.
1599
 
1600
GDB also now accepts a variety of C++ mangled symbol formats.  They are
1601
the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1602
You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1603
lucid, cfront, auto}'.  'gnu' is the default.  Do a 'set demangle-style foo'
1604
for the list of formats.
1605
 
1606
 * G++ symbol mangling problem
1607
 
1608
Recent versions of gcc have a bug in how they emit debugging information for
1609
C++ methods (when using dbx-style stabs).  The file 'gcc.patch' (in this
1610
directory) can be applied to gcc to fix the problem.  Alternatively, if you
1611
can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1612
usual symptom is difficulty with setting breakpoints on methods.  GDB complains
1613
about the method being non-existent.  (We believe that version 2.2.2 of GCC has
1614
this problem.)
1615
 
1616
 * New 'maintenance' command
1617
 
1618
All of the commands related to hacking GDB internals have been moved out of
1619
the main command set, and now live behind the 'maintenance' command.  This
1620
can also be abbreviated as 'mt'.  The following changes were made:
1621
 
1622
        dump-me ->              maintenance dump-me
1623
        info all-breakpoints -> maintenance info breakpoints
1624
        printmsyms ->           maintenance print msyms
1625
        printobjfiles ->        maintenance print objfiles
1626
        printpsyms ->           maintenance print psymbols
1627
        printsyms ->            maintenance print symbols
1628
 
1629
The following commands are new:
1630
 
1631
        maintenance demangle    Call internal GDB demangler routine to
1632
                                demangle a C++ link name and prints the result.
1633
        maintenance print type  Print a type chain for a given symbol
1634
 
1635
 * Change to .gdbinit file processing
1636
 
1637
We now read the $HOME/.gdbinit file before processing the argv arguments
1638
(e.g. reading symbol files or core files).  This allows global parameters to
1639
be set, which will apply during the symbol reading.  The ./.gdbinit is still
1640
read after argv processing.
1641
 
1642
 * New hosts supported
1643
 
1644
Solaris-2.0 !!!                         sparc-sun-solaris2  or  sun4sol2
1645
 
1646
GNU/Linux support                       i386-unknown-linux  or  linux
1647
 
1648
We are also including code to support the HP/PA running BSD and HPUX.  This
1649
is almost guaranteed not to work, as we didn't have time to test or build it
1650
for this release.  We are including it so that the more adventurous (or
1651
masochistic) of you can play with it.  We also had major problems with the
1652
fact that the compiler that we got from HP doesn't support the -g option.
1653
It costs extra.
1654
 
1655
 * New targets supported
1656
 
1657
Hitachi H8/300                          h8300-hitachi-hms  or  h8300hms
1658
 
1659
 * More smarts about finding #include files
1660
 
1661
GDB now remembers the compilation directory for all include files, and for
1662
all files from which C is generated (like yacc and lex sources).  This
1663
greatly improves GDB's ability to find yacc/lex sources, and include files,
1664
especially if you are debugging your program from a directory different from
1665
the one that contains your sources.
1666
 
1667
We also fixed a bug which caused difficulty with listing and setting
1668
breakpoints in include files which contain C code.  (In the past, you had to
1669
try twice in order to list an include file that you hadn't looked at before.)
1670
 
1671
 * Interesting infernals change
1672
 
1673
GDB now deals with arbitrary numbers of sections, where the symbols for each
1674
section must be relocated relative to that section's landing place in the
1675
target's address space.  This work was needed to support ELF with embedded
1676
stabs used by Solaris-2.0.
1677
 
1678
 * Bug fixes (of course!)
1679
 
1680
There have been loads of fixes for the following things:
1681
        mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1682
        i960, stabs, DOS(GO32), procfs, etc...
1683
 
1684
See the ChangeLog for details.
1685
 
1686
*** Changes in GDB-4.5:
1687
 
1688
 * New machines supported (host and target)
1689
 
1690
IBM RS6000 running AIX                  rs6000-ibm-aix  or rs6000
1691
 
1692
SGI Irix-4.x                            mips-sgi-irix4  or iris4
1693
 
1694
 * New malloc package
1695
 
1696
GDB now uses a new memory manager called mmalloc, based on gmalloc.
1697
Mmalloc is capable of handling mutiple heaps of memory.  It is also
1698
capable of saving a heap to a file, and then mapping it back in later.
1699
This can be used to greatly speedup the startup of GDB by using a
1700
pre-parsed symbol table which lives in a mmalloc managed heap.  For
1701
more details, please read mmalloc/mmalloc.texi.
1702
 
1703
 * info proc
1704
 
1705
The 'info proc' command (SVR4 only) has been enhanced quite a bit.  See
1706
'help info proc' for details.
1707
 
1708
 * MIPS ecoff symbol table format
1709
 
1710
The code that reads MIPS symbol table format is now supported on all hosts.
1711
Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1712
possible.
1713
 
1714
 * File name changes for MS-DOS
1715
 
1716
Many files in the config directories have been renamed to make it easier to
1717
support GDB on MS-DOSe systems (which have very restrictive file name
1718
conventions :-( ).  MS-DOSe host support (under DJ Delorie's GO32
1719
environment) is close to working but has some remaining problems.  Note
1720
that debugging of DOS programs is not supported, due to limitations
1721
in the ``operating system'', but it can be used to host cross-debugging.
1722
 
1723
 * Cross byte order fixes
1724
 
1725
Many fixes have been made to support cross debugging of Sparc and MIPS
1726
targets from hosts whose byte order differs.
1727
 
1728
 * New -mapped and -readnow options
1729
 
1730
If memory-mapped files are available on your system through the 'mmap'
1731
system call, you can use the -mapped option on the `file' or
1732
`symbol-file' commands to cause GDB to write the symbols from your
1733
program into a reusable file.  If the program you are debugging is
1734
called `/path/fred', the mapped symbol file will be `./fred.syms'.
1735
Future GDB debugging sessions will notice the presence of this file,
1736
and will quickly map in symbol information from it, rather than reading
1737
the symbol table from the executable program.  Using the '-mapped'
1738
option in a GDB `file' or `symbol-file' command has the same effect as
1739
starting GDB with the '-mapped' command-line option.
1740
 
1741
You can cause GDB to read the entire symbol table immediately by using
1742
the '-readnow' option with any of the commands that load symbol table
1743
information (or on the GDB command line).  This makes the command
1744
slower, but makes future operations faster.
1745
 
1746
The -mapped and -readnow options are typically combined in order to
1747
build a `fred.syms' file that contains complete symbol information.
1748
A simple GDB invocation to do nothing but build a `.syms' file for future
1749
use is:
1750
 
1751
        gdb -batch -nx -mapped -readnow programname
1752
 
1753
The `.syms' file is specific to the host machine on which GDB is run.
1754
It holds an exact image of GDB's internal symbol table.  It cannot be
1755
shared across multiple host platforms.
1756
 
1757
 * longjmp() handling
1758
 
1759
GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1760
siglongjmp() without losing control.  This feature has not yet been ported to
1761
all systems.  It currently works on many 386 platforms, all MIPS-based
1762
platforms (SGI, DECstation, etc), and Sun3/4.
1763
 
1764
 * Solaris 2.0
1765
 
1766
Preliminary work has been put in to support the new Solaris OS from Sun.  At
1767
this time, it can control and debug processes, but it is not capable of
1768
reading symbols.
1769
 
1770
 * Bug fixes
1771
 
1772
As always, many many bug fixes.  The major areas were with g++, and mipsread.
1773
People using the MIPS-based platforms should experience fewer mysterious
1774
crashes and trashed symbol tables.
1775
 
1776
*** Changes in GDB-4.4:
1777
 
1778
 * New machines supported (host and target)
1779
 
1780
SCO Unix on i386 IBM PC clones          i386-sco-sysv   or  i386sco
1781
        (except core files)
1782
BSD Reno on Vax                         vax-dec-bsd
1783
Ultrix on Vax                           vax-dec-ultrix
1784
 
1785
 * New machines supported (target)
1786
 
1787
AMD 29000 embedded, using EBMON         a29k-none-none
1788
 
1789
 * C++ support
1790
 
1791
GDB continues to improve its handling of C++.  `References' work better.
1792
The demangler has also been improved, and now deals with symbols mangled as
1793
per the Annotated C++ Reference Guide.
1794
 
1795
GDB also now handles `stabs' symbol information embedded in MIPS
1796
`ecoff' symbol tables.  Since the ecoff format was not easily
1797
extensible to handle new languages such as C++, this appeared to be a
1798
good way to put C++ debugging info into MIPS binaries.  This option
1799
will be supported in the GNU C compiler, version 2, when it is
1800
released.
1801
 
1802
 * New features for SVR4
1803
 
1804
GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1805
shared libraries.  Debugging dynamically linked programs should present
1806
only minor differences from debugging statically linked programs.
1807
 
1808
The `info proc' command will print out information about any process
1809
on an SVR4 system (including the one you are debugging).  At the moment,
1810
it prints the address mappings of the process.
1811
 
1812
If you bring up GDB on another SVR4 system, please send mail to
1813
bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1814
 
1815
 * Better dynamic linking support in SunOS
1816
 
1817
Reading symbols from shared libraries which contain debugging symbols
1818
now works properly.  However, there remain issues such as automatic
1819
skipping of `transfer vector' code during function calls, which
1820
make it harder to debug code in a shared library, than to debug the
1821
same code linked statically.
1822
 
1823
 * New Getopt
1824
 
1825
GDB is now using the latest `getopt' routines from the FSF.  This
1826
version accepts the -- prefix for options with long names.  GDB will
1827
continue to accept the old forms (-option and +option) as well.
1828
Various single letter abbreviations for options have been explicity
1829
added to the option table so that they won't get overshadowed in the
1830
future by other options that begin with the same letter.
1831
 
1832
 * Bugs fixed
1833
 
1834
The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1835
Many assorted bugs have been handled.  Many more remain to be handled.
1836
See the various ChangeLog files (primarily in gdb and bfd) for details.
1837
 
1838
 
1839
*** Changes in GDB-4.3:
1840
 
1841
 * New machines supported (host and target)
1842
 
1843
Amiga 3000 running Amix                 m68k-cbm-svr4   or  amix
1844
NCR 3000 386 running SVR4               i386-ncr-svr4   or  ncr3000
1845
Motorola Delta 88000 running Sys V      m88k-motorola-sysv  or  delta88
1846
 
1847
 * Almost SCO Unix support
1848
 
1849
We had hoped to support:
1850
SCO Unix on i386 IBM PC clones          i386-sco-sysv   or  i386sco
1851
(except for core file support), but we discovered very late in the release
1852
that it has problems with process groups that render gdb unusable.  Sorry
1853
about that.  I encourage people to fix it and post the fixes.
1854
 
1855
 * Preliminary ELF and DWARF support
1856
 
1857
GDB can read ELF object files on System V Release 4, and can handle
1858
debugging records for C, in DWARF format, in ELF files.  This support
1859
is preliminary.  If you bring up GDB on another SVR4 system, please
1860
send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1861
reqired (if any).
1862
 
1863
 * New Readline
1864
 
1865
GDB now uses the latest `readline' library.  One user-visible change
1866
is that two tabs will list possible command completions, which previously
1867
required typing M-? (meta-question mark, or ESC ?).
1868
 
1869
 * Bugs fixed
1870
 
1871
The `stepi' bug that many of you noticed has been squashed.
1872
Many bugs in C++ have been handled.  Many more remain to be handled.
1873
See the various ChangeLog files (primarily in gdb and bfd) for details.
1874
 
1875
 * State of the MIPS world (in case you wondered):
1876
 
1877
GDB can understand the symbol tables emitted by the compilers
1878
supplied by most vendors of MIPS-based machines, including DEC.  These
1879
symbol tables are in a format that essentially nobody else uses.
1880
 
1881
Some versions of gcc come with an assembler post-processor called
1882
mips-tfile.  This program is required if you want to do source-level
1883
debugging of gcc-compiled programs.  I believe FSF does not ship
1884
mips-tfile with gcc version 1, but it will eventually come with gcc
1885
version 2.
1886
 
1887
Debugging of g++ output remains a problem.  g++ version 1.xx does not
1888
really support it at all.  (If you're lucky, you should be able to get
1889
line numbers and stack traces to work, but no parameters or local
1890
variables.)  With some work it should be possible to improve the
1891
situation somewhat.
1892
 
1893
When gcc version 2 is released, you will have somewhat better luck.
1894
However, even then you will get confusing results for inheritance and
1895
methods.
1896
 
1897
We will eventually provide full debugging of g++ output on
1898
DECstations.  This will probably involve some kind of stabs-in-ecoff
1899
encapulation, but the details have not been worked out yet.
1900
 
1901
 
1902
*** Changes in GDB-4.2:
1903
 
1904
 *  Improved configuration
1905
 
1906
Only one copy of `configure' exists now, and it is not self-modifying.
1907
Porting BFD is simpler.
1908
 
1909
 *  Stepping improved
1910
 
1911
The `step' and `next' commands now only stop at the first instruction
1912
of a source line.  This prevents the multiple stops that used to occur
1913
in switch statements, for-loops, etc.  `Step' continues to stop if a
1914
function that has debugging information is called within the line.
1915
 
1916
 *  Bug fixing
1917
 
1918
Lots of small bugs fixed.  More remain.
1919
 
1920
 *  New host supported (not target)
1921
 
1922
Intel 386 PC clone running Mach         i386-none-mach
1923
 
1924
 
1925
*** Changes in GDB-4.1:
1926
 
1927
 *  Multiple source language support
1928
 
1929
GDB now has internal scaffolding to handle several source languages.
1930
It determines the type of each source file from its filename extension,
1931
and will switch expression parsing and number formatting to match the
1932
language of the function in the currently selected stack frame.
1933
You can also specifically set the language to be used, with
1934
`set language c' or `set language modula-2'.
1935
 
1936
 *  GDB and Modula-2
1937
 
1938
GDB now has preliminary support for the GNU Modula-2 compiler,
1939
currently under development at the State University of New York at
1940
Buffalo.  Development of both GDB and the GNU Modula-2 compiler will
1941
continue through the fall of 1991 and into 1992.
1942
 
1943
Other Modula-2 compilers are currently not supported, and attempting to
1944
debug programs compiled with them will likely result in an error as the
1945
symbol table is read.  Feel free to work on it, though!
1946
 
1947
There are hooks in GDB for strict type checking and range checking,
1948
in the `Modula-2 philosophy', but they do not currently work.
1949
 
1950
 * set write on/off
1951
 
1952
GDB can now write to executable and core files (e.g. patch
1953
a variable's value).   You must turn this switch on, specify
1954
the file ("exec foo" or "core foo"), *then* modify it, e.g.
1955
by assigning a new value to a variable.  Modifications take
1956
effect immediately.
1957
 
1958
 * Automatic SunOS shared library reading
1959
 
1960
When you run your program, GDB automatically determines where its
1961
shared libraries (if any) have been loaded, and reads their symbols.
1962
The `share' command is no longer needed.  This also works when
1963
examining core files.
1964
 
1965
 * set listsize
1966
 
1967
You can specify the number of lines that the `list' command shows.
1968
The default is 10.
1969
 
1970
 * New machines supported (host and target)
1971
 
1972
SGI Iris (MIPS) running Irix V3:        mips-sgi-irix   or  iris
1973
Sony NEWS (68K) running NEWSOS 3.x:     m68k-sony-sysv  or  news
1974
Ultracomputer (29K) running Sym1:       a29k-nyu-sym1   or  ultra3
1975
 
1976
 * New hosts supported (not targets)
1977
 
1978
IBM RT/PC:                              romp-ibm-aix    or  rtpc
1979
 
1980
 * New targets supported (not hosts)
1981
 
1982
AMD 29000 embedded with COFF            a29k-none-coff
1983
AMD 29000 embedded with a.out           a29k-none-aout
1984
Ultracomputer remote kernel debug       a29k-nyu-kern
1985
 
1986
 * New remote interfaces
1987
 
1988
AMD 29000 Adapt
1989
AMD 29000 Minimon
1990
 
1991
 
1992
*** Changes in GDB-4.0:
1993
 
1994
 *  New Facilities
1995
 
1996
Wide output is wrapped at good places to make the output more readable.
1997
 
1998
Gdb now supports cross-debugging from a host machine of one type to a
1999
target machine of another type.  Communication with the target system
2000
is over serial lines.  The ``target'' command handles connecting to the
2001
remote system; the ``load'' command will download a program into the
2002
remote system.  Serial stubs for the m68k and i386 are provided.  Gdb
2003
also supports debugging of realtime processes running under VxWorks,
2004
using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2005
stub on the target system.
2006
 
2007
New CPUs supported include the AMD 29000 and Intel 960.
2008
 
2009
GDB now reads object files and symbol tables via a ``binary file''
2010
library, which allows a single copy of GDB to debug programs of multiple
2011
object file types such as a.out and coff.
2012
 
2013
There is now a GDB reference card in "doc/refcard.tex".  (Make targets
2014
refcard.dvi and refcard.ps are available to format it).
2015
 
2016
 
2017
 *  Control-Variable user interface simplified
2018
 
2019
All variables that control the operation of the debugger can be set
2020
by the ``set'' command, and displayed by the ``show'' command.
2021
 
2022
For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2023
``Show prompt'' produces the response:
2024
Gdb's prompt is new-gdb=>.
2025
 
2026
What follows are the NEW set commands.  The command ``help set'' will
2027
print a complete list of old and new set commands.  ``help set FOO''
2028
will give a longer description of the variable FOO.  ``show'' will show
2029
all of the variable descriptions and their current settings.
2030
 
2031
confirm on/off:  Enables warning questions for operations that are
2032
                 hard to recover from, e.g. rerunning the program while
2033
                 it is already running.  Default is ON.
2034
 
2035
editing on/off:  Enables EMACS style command line editing
2036
                 of input.  Previous lines can be recalled with
2037
                 control-P, the current line can be edited with control-B,
2038
                 you can search for commands with control-R, etc.
2039
                 Default is ON.
2040
 
2041
history filename NAME:  NAME is where the gdb command history
2042
                        will be stored.  The default is .gdb_history,
2043
                        or the value of the environment variable
2044
                        GDBHISTFILE.
2045
 
2046
history size N:  The size, in commands, of the command history.  The
2047
                 default is 256, or the value of the environment variable
2048
                 HISTSIZE.
2049
 
2050
history save on/off: If this value is set to ON, the history file will
2051
                      be saved after exiting gdb.  If set to OFF, the
2052
                      file will not be saved.  The default is OFF.
2053
 
2054
history expansion on/off: If this value is set to ON, then csh-like
2055
                          history expansion will be performed  on
2056
                          command line input.  The default is OFF.
2057
 
2058
radix N:  Sets the default radix for input and output.  It can be set
2059
          to 8, 10, or 16.  Note that the argument to "radix" is interpreted
2060
          in the current radix, so "set radix 10" is always a no-op.
2061
 
2062
height N: This integer value is the number of lines on a page. Default
2063
          is 24, the current `stty rows'' setting, or the ``li#''
2064
          setting from the termcap entry matching the environment
2065
          variable TERM.
2066
 
2067
width N:  This integer value is the number of characters on a line.
2068
          Default is 80, the current `stty cols'' setting, or the ``co#''
2069
          setting from the termcap entry matching the environment
2070
          variable TERM.
2071
 
2072
Note: ``set screensize'' is obsolete. Use ``set height'' and
2073
``set width'' instead.
2074
 
2075
print address on/off:  Print memory addresses in various command displays,
2076
                      such as stack traces and structure values.  Gdb looks
2077
                      more ``symbolic'' if you turn this off; it looks more
2078
                      ``machine level'' with it on.  Default is ON.
2079
 
2080
print array on/off:  Prettyprint arrays.  New convenient format!  Default
2081
                    is OFF.
2082
 
2083
print demangle on/off:   Print C++ symbols in "source" form if on,
2084
                        "raw" form if off.
2085
 
2086
print asm-demangle on/off:  Same, for assembler level printouts
2087
                        like instructions.
2088
 
2089
print vtbl on/off:  Prettyprint C++ virtual function tables.  Default is OFF.
2090
 
2091
 
2092
 *  Support for Epoch Environment.
2093
 
2094
The epoch environment is a version of Emacs v18 with windowing.  One
2095
new command, ``inspect'', is identical to ``print'', except that if you
2096
are running in the epoch environment, the value is printed in its own
2097
window.
2098
 
2099
 
2100
 *  Support for Shared Libraries
2101
 
2102
GDB can now debug programs and core files that use SunOS shared libraries.
2103
Symbols from a shared library cannot be referenced
2104
before the shared library has been linked with the program (this
2105
happens after you type ``run'' and before the function main() is entered).
2106
At any time after this linking (including when examining core files
2107
from dynamically linked programs), gdb reads the symbols from each
2108
shared library when you type the ``sharedlibrary'' command.
2109
It can be abbreviated ``share''.
2110
 
2111
sharedlibrary REGEXP:  Load shared object library symbols for files
2112
                       matching a unix regular expression.  No argument
2113
                       indicates to load symbols for all shared libraries.
2114
 
2115
info sharedlibrary:  Status of loaded shared libraries.
2116
 
2117
 
2118
 *  Watchpoints
2119
 
2120
A watchpoint stops execution of a program whenever the value of an
2121
expression changes.  Checking for this slows down execution
2122
tremendously whenever you are in the scope of the expression, but is
2123
quite useful for catching tough ``bit-spreader'' or pointer misuse
2124
problems.  Some machines such as the 386 have hardware for doing this
2125
more quickly, and future versions of gdb will use this hardware.
2126
 
2127
watch EXP:  Set a watchpoint (breakpoint) for an expression.
2128
 
2129
info watchpoints:  Information about your watchpoints.
2130
 
2131
delete N:   Deletes watchpoint number N (same as breakpoints).
2132
disable N:  Temporarily turns off watchpoint number N (same as breakpoints).
2133
enable N:   Re-enables watchpoint number N (same as breakpoints).
2134
 
2135
 
2136
 *  C++ multiple inheritance
2137
 
2138
When used with a GCC version 2 compiler, GDB supports multiple inheritance
2139
for C++ programs.
2140
 
2141
 *  C++ exception handling
2142
 
2143
Gdb now supports limited C++ exception handling.  Besides the existing
2144
ability to breakpoint on an exception handler, gdb can breakpoint on
2145
the raising of an exception (before the stack is peeled back to the
2146
handler's context).
2147
 
2148
catch FOO:  If there is a FOO exception handler in the dynamic scope,
2149
            set a breakpoint to catch exceptions which may be raised there.
2150
            Multiple exceptions (``catch foo bar baz'') may be caught.
2151
 
2152
info catch:  Lists all exceptions which may be caught in the
2153
             current stack frame.
2154
 
2155
 
2156
 *  Minor command changes
2157
 
2158
The command ``call func (arg, arg, ...)'' now acts like the print
2159
command, except it does not print or save a value if the function's result
2160
is void.  This is similar to dbx usage.
2161
 
2162
The ``up'' and ``down'' commands now always print the frame they end up
2163
at; ``up-silently'' and `down-silently'' can be used in scripts to change
2164
frames without printing.
2165
 
2166
 *  New directory command
2167
 
2168
'dir' now adds directories to the FRONT of the source search path.
2169
The path starts off empty.  Source files that contain debug information
2170
about the directory in which they were compiled can be found even
2171
with an empty path; Sun CC and GCC include this information.  If GDB can't
2172
find your source file in the current directory, type "dir .".
2173
 
2174
 * Configuring GDB for compilation
2175
 
2176
For normal use, type ``./configure host''.  See README or gdb.texinfo
2177
for more details.
2178
 
2179
GDB now handles cross debugging.  If you are remotely debugging between
2180
two different machines, type ``./configure host -target=targ''.
2181
Host is the machine where GDB will run; targ is the machine
2182
where the program that you are debugging will run.

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.