* GDB 4.18 released
1999-04-13 10:48 GDB 4.18 released Jim Blandy
@ 1999-04-13 9:04 ` Jim Blandy
0 siblings, 0 replies; 2+ messages in thread
From: Jim Blandy @ 1999-04-13 9:04 UTC (permalink / raw)
To: gdb, gdb-testers
GDB 4.18 is released!
Version 4.18 of GDB, the GNU Debugger, is now available via anonymous FTP.
GDB is a source-level debugger for C, C++, and many other languages. GDB can
target (i.e. debug programs running on) dozens of different processor
architectures, and GDB itself can run on most popular Unix variants, Windows
NT, and Windows 95.
You can download GDB from either Project GNU's FTP server or any of its
mirrors, or Cygnus's Sourceware site:
ftp://ftp.gnu.org/pub/gnu/gdb
ftp://sourceware.cygnus.com/pub/gdb
The previous version, 4.17, was released about a year ago; there have been
many changes and additions since then. Details are below.
The vital stats:
-rw-r--r-- 1 jimb cygnus 11657032 Apr 7 16:44 gdb-4.18.tar.gz
The md5sum checksum is:
828d28487af6cec074639c1102569473 gdb-4.18.tar.gz
There is a web page for GDB at:
http://sourceware.cygnus.com/gdb/
That page includes information about GDB mailing lists (an announcement
mailing list, developers discussion lists, etc.), locations for development
snapshots, preformatted documentation, and links to related information
around the net. We will put errata notes and host-specific tips for this
release on-line as any problems come up. All mailing lists archives are also
browsable via the web.
Many people have contributed to this release. Thanks to everybody for the
help!
Keep those fixes and improvements coming in! (Send them to
bug-gdb@prep.ai.mit.edu)
Jim Blandy and the rest of the Cygnus GDB Team
Cygnus Solutions
*** Changes in GDB-4.18:
* New native configurations
HP-UX 10.20 hppa*-*-hpux10.20
HP-UX 11.x hppa*-*-hpux11.0*
M68K Linux m68*-*-linux*
* New targets
Fujitsu FR30 fr30-*-elf*
Intel StrongARM strongarm-*-*
Mitsubishi D30V d30v-*-*
* OBSOLETE configurations
Gould PowerNode, NP1 np1-*-*, pn-*-*
Configurations that have been declared obsolete will be commented out,
but the code will be left in place. If there is no activity to revive
these configurations before the next release of GDB, the sources will
be permanently REMOVED.
* ANSI/ISO C
As a compatibility experiment, GDB's source files buildsym.h and
buildsym.c have been converted to pure standard C, no longer
containing any K&R compatibility code. We believe that all systems in
use today either come with a standard C compiler, or have a GCC port
available. If this is not true, please report the affected
configuration to bug-gdb@gnu.org immediately. See the README file for
information about getting a standard C compiler if you don't have one
already.
* Readline 2.2
GDB now uses readline 2.2.
* set extension-language
You can now control the mapping between filename extensions and source
languages by using the `set extension-language' command. For instance,
you can ask GDB to treat .c files as C++ by saying
set extension-language .c c++
The command `info extensions' lists all of the recognized extensions
and their associated languages.
* Setting processor type for PowerPC and RS/6000
When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
you can use the `set processor' command to specify what variant of the
PowerPC family you are debugging. The command
set processor NAME
sets the PowerPC/RS6000 variant to NAME. GDB knows about the
following PowerPC and RS6000 variants:
ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
rs6000 IBM RS6000 ("POWER") architecture, user-level view
403 IBM PowerPC 403
403GC IBM PowerPC 403GC
505 Motorola PowerPC 505
860 Motorola PowerPC 860 or 850
601 Motorola PowerPC 601
602 Motorola PowerPC 602
603 Motorola/IBM PowerPC 603 or 603e
604 Motorola PowerPC 604 or 604e
750 Motorola/IBM PowerPC 750 or 750
At the moment, this command just tells GDB what to name the
special-purpose processor registers. Since almost all the affected
registers are inaccessible to user-level programs, this command is
only useful for remote debugging in its present form.
* HP-UX support
Thanks to a major code donation from Hewlett-Packard, GDB now has much
more extensive support for HP-UX. Added features include shared
library support, kernel threads and hardware watchpoints for 11.00,
support for HP's ANSI C and C++ compilers, and a compatibility mode
for xdb and dbx commands.
* Catchpoints
HP's donation includes the new concept of catchpoints, which is a
generalization of the old catch command. On HP-UX, it is now possible
to catch exec, fork, and vfork, as well as library loading.
This means that the existing catch command has changed; its first
argument now specifies the type of catch to be set up. See the
output of "help catch" for a list of catchpoint types.
* Debugging across forks
On HP-UX, you can choose which process to debug when a fork() happens
in the inferior.
* TUI
HP has donated a curses-based terminal user interface (TUI). To get
it, build with --enable-tui. Although this can be enabled for any
configuration, at present it only works for native HP debugging.
* GDB remote protocol additions
A new protocol packet 'X' that writes binary data is now available.
Default behavior is to try 'X', then drop back to 'M' if the stub
fails to respond. The settable variable `remotebinarydownload'
allows explicit control over the use of 'X'.
For 64-bit targets, the memory packets ('M' and 'm') can now contain a
full 64-bit address. The command
set remoteaddresssize 32
can be used to revert to the old behaviour. For existing remote stubs
the change should not be noticed, as the additional address information
will be discarded.
In order to assist in debugging stubs, you may use the maintenance
command `packet' to send any text string to the stub. For instance,
maint packet heythere
sends the packet "$heythere#<checksum>". Note that it is very easy to
disrupt a debugging session by sending the wrong packet at the wrong
time.
The compare-sections command allows you to compare section data on the
target to what is in the executable file without uploading or
downloading, by comparing CRC checksums.
* Tracing can collect general expressions
You may now collect general expressions at tracepoints. This requires
further additions to the target-side stub; see tracepoint.c and
doc/agentexpr.texi for further details.
* mask-address variable for Mips
For Mips targets, you may control the zeroing of the upper 32 bits of
a 64-bit address by entering `set mask-address on'. This is mainly
of interest to users of embedded R4xxx and R5xxx processors.
* Higher serial baud rates
GDB's serial code now allows you to specify baud rates 57600, 115200,
230400, and 460800 baud. (Note that your host system may not be able
to achieve all of these rates.)
* i960 simulator
The i960 configuration now includes an initial implementation of a
builtin simulator, contributed by Jim Wilson.
^ permalink raw reply [flat|nested] 2+ messages in thread
* GDB 4.18 released
@ 1999-04-13 10:48 Jim Blandy
1999-04-13 9:04 ` Jim Blandy
0 siblings, 1 reply; 2+ messages in thread
From: Jim Blandy @ 1999-04-13 10:48 UTC (permalink / raw)
To: gdb, gdb-testers
GDB 4.18 is released!
Version 4.18 of GDB, the GNU Debugger, is now available via anonymous FTP.
GDB is a source-level debugger for C, C++, and many other languages. GDB can
target (i.e. debug programs running on) dozens of different processor
architectures, and GDB itself can run on most popular Unix variants, Windows
NT, and Windows 95.
You can download GDB from either Project GNU's FTP server or any of its
mirrors, or Cygnus's Sourceware site:
ftp://ftp.gnu.org/pub/gnu/gdb
ftp://sourceware.cygnus.com/pub/gdb
The previous version, 4.17, was released about a year ago; there have been
many changes and additions since then. Details are below.
The vital stats:
-rw-r--r-- 1 jimb cygnus 11657032 Apr 7 16:44 gdb-4.18.tar.gz
The md5sum checksum is:
828d28487af6cec074639c1102569473 gdb-4.18.tar.gz
There is a web page for GDB at:
http://sourceware.cygnus.com/gdb/
That page includes information about GDB mailing lists (an announcement
mailing list, developers discussion lists, etc.), locations for development
snapshots, preformatted documentation, and links to related information
around the net. We will put errata notes and host-specific tips for this
release on-line as any problems come up. All mailing lists archives are also
browsable via the web.
Many people have contributed to this release. Thanks to everybody for the
help!
Keep those fixes and improvements coming in! (Send them to
bug-gdb@prep.ai.mit.edu)
Jim Blandy and the rest of the Cygnus GDB Team
Cygnus Solutions
*** Changes in GDB-4.18:
* New native configurations
HP-UX 10.20 hppa*-*-hpux10.20
HP-UX 11.x hppa*-*-hpux11.0*
M68K Linux m68*-*-linux*
* New targets
Fujitsu FR30 fr30-*-elf*
Intel StrongARM strongarm-*-*
Mitsubishi D30V d30v-*-*
* OBSOLETE configurations
Gould PowerNode, NP1 np1-*-*, pn-*-*
Configurations that have been declared obsolete will be commented out,
but the code will be left in place. If there is no activity to revive
these configurations before the next release of GDB, the sources will
be permanently REMOVED.
* ANSI/ISO C
As a compatibility experiment, GDB's source files buildsym.h and
buildsym.c have been converted to pure standard C, no longer
containing any K&R compatibility code. We believe that all systems in
use today either come with a standard C compiler, or have a GCC port
available. If this is not true, please report the affected
configuration to bug-gdb@gnu.org immediately. See the README file for
information about getting a standard C compiler if you don't have one
already.
* Readline 2.2
GDB now uses readline 2.2.
* set extension-language
You can now control the mapping between filename extensions and source
languages by using the `set extension-language' command. For instance,
you can ask GDB to treat .c files as C++ by saying
set extension-language .c c++
The command `info extensions' lists all of the recognized extensions
and their associated languages.
* Setting processor type for PowerPC and RS/6000
When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
you can use the `set processor' command to specify what variant of the
PowerPC family you are debugging. The command
set processor NAME
sets the PowerPC/RS6000 variant to NAME. GDB knows about the
following PowerPC and RS6000 variants:
ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
rs6000 IBM RS6000 ("POWER") architecture, user-level view
403 IBM PowerPC 403
403GC IBM PowerPC 403GC
505 Motorola PowerPC 505
860 Motorola PowerPC 860 or 850
601 Motorola PowerPC 601
602 Motorola PowerPC 602
603 Motorola/IBM PowerPC 603 or 603e
604 Motorola PowerPC 604 or 604e
750 Motorola/IBM PowerPC 750 or 750
At the moment, this command just tells GDB what to name the
special-purpose processor registers. Since almost all the affected
registers are inaccessible to user-level programs, this command is
only useful for remote debugging in its present form.
* HP-UX support
Thanks to a major code donation from Hewlett-Packard, GDB now has much
more extensive support for HP-UX. Added features include shared
library support, kernel threads and hardware watchpoints for 11.00,
support for HP's ANSI C and C++ compilers, and a compatibility mode
for xdb and dbx commands.
* Catchpoints
HP's donation includes the new concept of catchpoints, which is a
generalization of the old catch command. On HP-UX, it is now possible
to catch exec, fork, and vfork, as well as library loading.
This means that the existing catch command has changed; its first
argument now specifies the type of catch to be set up. See the
output of "help catch" for a list of catchpoint types.
* Debugging across forks
On HP-UX, you can choose which process to debug when a fork() happens
in the inferior.
* TUI
HP has donated a curses-based terminal user interface (TUI). To get
it, build with --enable-tui. Although this can be enabled for any
configuration, at present it only works for native HP debugging.
* GDB remote protocol additions
A new protocol packet 'X' that writes binary data is now available.
Default behavior is to try 'X', then drop back to 'M' if the stub
fails to respond. The settable variable `remotebinarydownload'
allows explicit control over the use of 'X'.
For 64-bit targets, the memory packets ('M' and 'm') can now contain a
full 64-bit address. The command
set remoteaddresssize 32
can be used to revert to the old behaviour. For existing remote stubs
the change should not be noticed, as the additional address information
will be discarded.
In order to assist in debugging stubs, you may use the maintenance
command `packet' to send any text string to the stub. For instance,
maint packet heythere
sends the packet "$heythere#<checksum>". Note that it is very easy to
disrupt a debugging session by sending the wrong packet at the wrong
time.
The compare-sections command allows you to compare section data on the
target to what is in the executable file without uploading or
downloading, by comparing CRC checksums.
* Tracing can collect general expressions
You may now collect general expressions at tracepoints. This requires
further additions to the target-side stub; see tracepoint.c and
doc/agentexpr.texi for further details.
* mask-address variable for Mips
For Mips targets, you may control the zeroing of the upper 32 bits of
a 64-bit address by entering `set mask-address on'. This is mainly
of interest to users of embedded R4xxx and R5xxx processors.
* Higher serial baud rates
GDB's serial code now allows you to specify baud rates 57600, 115200,
230400, and 460800 baud. (Note that your host system may not be able
to achieve all of these rates.)
* i960 simulator
The i960 configuration now includes an initial implementation of a
builtin simulator, contributed by Jim Wilson.
From jkj@sco.com Tue Apr 13 16:11:00 1999
From: "J. Kean Johnston" <jkj@sco.com>
To: GDB Developers List <gdb@cygnus.com>
Subject: OSR5 success
Date: Tue, 13 Apr 1999 16:11:00 -0000
Message-id: <19990413144019.B10398@sco.com>
X-SW-Source: 1999-04/msg00025.html
Content-length: 498
All,
4.17.87 is now working (at least a cursory test passes) on OSR5.
I am doing a full testsuite run now, but I am glad to announce that
it can at least insert breakpoints :-)
Good work to whoever actually fixed this :-)
--
J. Kean Johnston | "Only the dead have seen an end to war"
Engineer, SPG | -- Plato
Santa Cruz, CA +----------------------------------------------------------
Tel: 831-427-7569 Fax: 831-429-1887 E-mail: jkj@sco.com
From shebs@cygnus.com Tue Apr 13 16:55:00 1999
From: Stan Shebs <shebs@cygnus.com>
To: jkj@sco.com
Cc: gdb@cygnus.com
Subject: Re: OSR5 success
Date: Tue, 13 Apr 1999 16:55:00 -0000
Message-id: <199904132316.QAA14004@andros.cygnus.com>
References: <19990413144019.B10398@sco.com>
X-SW-Source: 1999-04/msg00026.html
Content-length: 351
Date: Tue, 13 Apr 1999 14:40:20 -0700
From: "J. Kean Johnston" <jkj@sco.com>
4.17.87 is now working (at least a cursory test passes) on OSR5.
I am doing a full testsuite run now, but I am glad to announce that
it can at least insert breakpoints :-)
Great! And hopefully nothing got crumbled between 4.17.87 and 4.18...
Stan
From ac131313@cygnus.com Tue Apr 13 21:57:00 1999
From: Andrew Cagney <ac131313@cygnus.com>
To: "M. David Gelbman" <dgelbman@npiny.com>
Cc: gdb@cygnus.com
Subject: Re: Implimenting MIPS R4650 DWATCH register as hbreak hardware breakpoint
Date: Tue, 13 Apr 1999 21:57:00 -0000
Message-id: <37140E7B.955EBE89@cygnus.com>
References: <3707AE48.2582E501.cygnus.gdb@npiny.com>
X-SW-Source: 1999-04/msg00028.html
Content-length: 1075
"M. David Gelbman" wrote:
>
> Anybody,
>
> I'm developing an application on a an IDT MIPS R4650 based board. this
> MIPS CPU has a DWATCH register capable of breaking on a data read or
> write (or both).
>
> What must I do to the host portion of GDB to let it know my target is
> capable of implimenting a "hardware" breakpoint? Further what must I do
> to modify my target GDB stub?
>
> I suspect the host part is simply a re-configuration of somthing in the
> .gdbini file. I expect that the target stub needs to parse a new
> command in handle_exception() through the "target remote" protocol. But
> I haven't yet found the magic words.
FYI,
J.T. Conklin <jtc@redbacknetworks.com> recently posted a proposal (and
patch) to gdb/remote.c that adds hardware breakpoint suport.
At present the proposed protocol changes are accepted but the patch
needed some minor revisions.
Could I suggest finding the thread ``Patch to add breakpoint extension
to remote protocol'' on the gdb-patches mailing list. (Am I foolisly
assuming that gdb-patches is archived?)
Andrew
From ac131313@cygnus.com Tue Apr 13 21:57:00 1999
From: Andrew Cagney <ac131313@cygnus.com>
To: Stan Shebs <shebs@cygnus.com>
Cc: jtc@redback.com, gdb@cygnus.com
Subject: Re: remote protocol checksum and binary download
Date: Tue, 13 Apr 1999 21:57:00 -0000
Message-id: <37141350.CAEE414F@cygnus.com>
References: <5m7lrhl3rw.fsf@jtc.redbacknetworks.com> <199904130227.TAA17991.cygnus.gdb@andros.cygnus.com>
X-SW-Source: 1999-04/msg00027.html
Content-length: 1058
Stan Shebs wrote:
> Yes, the binary download option has been no end of trouble - it's a
> good reminder of why we do a 7-bit protocol in the first place! You've
> identified some real problems, and I expect that Andrew C. and others
> will mobilize to bash on them.
The very strong rumor I've been given is that Keith Seitz fixed the
problem before 4.18 went out the door. See:
1999-03-26 Jim Blandy <jimb@zwingli.cygnus.com>
Merged change from Keith Seitz:
1999-03-16 Keith Seitz <keiths@cygnus.com>
* remote.c (reomte_binary_checked): New file global.
(check_binary_download): New function to check if
stub supports binary downloading that works with
stubs that are not eight bit clean.
(remote_write_bytes): Check for binary download capability
and use it if available.
Remove references to global remote_binary_length. What a hack.
(putpkt_binary): New function.
(putpkt): Call putpkt_binary.
Use xor to escape trouble characters.
Andrew
From ac131313@cygnus.com Tue Apr 13 21:57:00 1999
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Drotos <drdani@mazsola.iit.uni-miskolc.hu>
Cc: gdb@cygnus.com
Subject: Re: native gdb+simulator
Date: Tue, 13 Apr 1999 21:57:00 -0000
Message-id: <371412FF.CD662E48@cygnus.com>
References: <199904130703.AAA16348@cygnus.com> <Pine.SO4.4.00.9904131055330.3707-100000.cygnus.gdb@mazsola>
X-SW-Source: 1999-04/msg00029.html
Content-length: 758
Daniel Drotos wrote:
>
> Hi,
>
> Is it possible to include a simultor if gdb is configured for the
> host's target?
Yes.
> I mean, for example I config and compile on elf32-i386 (e.g. linux)
> and I'd like to use this bfd target to read in the file to be
> debugged, but use a (own written) simulator to actually execute the
> code.
Yes.
> Is it possible to hack feature like this into the gdb without
> introducing a new bfd target?
Yes.
If there is a simulator in the .../sim directory and GDB knows about it
(see gdb/config/*/*.mt) it will be linked in. The file
include/remote-sim.h specifies the interface and the various sim
sub-directories contain examples.
Should I infer that there could be a GPL'd i386 simulator in the making?
Andrew
From jsm@cygnus.com Tue Apr 13 21:59:00 1999
From: Jason Molenda <jsm@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: "M. David Gelbman" <dgelbman@npiny.com>, gdb@cygnus.com
Subject: Re: Implimenting MIPS R4650 DWATCH register as hbreak hardware breakpoint
Date: Tue, 13 Apr 1999 21:59:00 -0000
Message-id: <19990413213617.A6630@cygnus.com>
References: <3707AE48.2582E501.cygnus.gdb@npiny.com> <37140E7B.955EBE89@cygnus.com> <37140E7B.955EBE89@cygnus.com>
X-SW-Source: 1999-04/msg00030.html
Content-length: 457
On Wed, Apr 14, 1999 at 01:41:47PM +1000, Andrew Cagney wrote:
> Could I suggest finding the thread ``Patch to add breakpoint extension
> to remote protocol'' on the gdb-patches mailing list. (Am I foolisly
> assuming that gdb-patches is archived?)
Of course it's archived.
http://sourceware.cygnus.com/ml/gdb-patches/1998/msg00121.html
The follow-up to JT's note is in the February archives,
http://sourceware.cygnus.com/ml/gdb-patches/1999-02/
J
From drdani@mazsola.iit.uni-miskolc.hu Wed Apr 14 02:41:00 1999
From: Daniel Drotos <drdani@mazsola.iit.uni-miskolc.hu>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@cygnus.com
Subject: Re: native gdb+simulator
Date: Wed, 14 Apr 1999 02:41:00 -0000
Message-id: <Pine.SO4.4.00.9904141046350.2278-100000@mazsola>
References: <371412FF.CD662E48@cygnus.com>
X-SW-Source: 1999-04/msg00031.html
Content-length: 800
On Wed, 14 Apr 1999, Andrew Cagney wrote:
[ ... ]
Thanks for the info!
> Should I infer that there could be a GPL'd i386 simulator in the making?
No. We are working on GPL'd development environment for MCS51 based
micros. C compiler is working now, simulator is ready too. It would be
nice to use gdb as a sphisticated interface to the simulator.
My idea is that hex file generated by the compiler/linker could be
placed in an empty elf file, for example in a .mcs51code section which
could be passed to the simulator by the gdb-sim interface. If the
compiler could produce debug info in stab format then it could be
included into that empty 'template' elf file too, so gdb could debug
it, I hope.
So it doesn't matter what the native target is, any kind of elf could
be usabe I think.
Daniel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-04-13 10:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-04-13 10:48 GDB 4.18 released Jim Blandy
1999-04-13 9:04 ` Jim Blandy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox