Paul N. Hilfinger 83e3a93c83 Have ptype handle types declared pragma Unchecked_Variants.
When a type is marked with pragma Unchecked_Variants, ptype did not print
variants having a single component, since the compiler produces incorrect
debugging output for such cases.  With this patch, we special-case these
components so that they print.

Changelog:

    * gdb/ada-typeprint.c (print_selected_record_field_types): New function,
    incorporating and generalizing print_record_field_types.
    (print_record_field_types): Change return value and update comment.
    Re-implement using print_selected_record_field_types.
    (print_choices): Print "=>" here.
    Handle case of unencoded variant branch.
    (print_variant_clauses): Reformat comment.
    Special-case unencoded variant branch.
2010-10-04 06:37:54 +00:00
2010-10-03 23:00:05 +00:00
2010-10-02 14:42:48 +00:00
2010-09-29 10:14:02 +00:00
2010-09-27 20:23:01 +00:00
2010-09-29 10:14:02 +00:00
2010-09-27 21:01:18 +00:00
2010-10-01 08:15:42 +00:00
2010-09-10 23:17:28 +00:00
2010-09-27 21:01:18 +00:00
2010-10-02 07:04:07 +00:00
/:
2010-06-01 17:53:40 +00:00
/:
2010-06-01 17:53:40 +00:00
2010-01-09 21:11:44 +00:00
2010-01-09 21:11:44 +00:00
2010-01-09 21:11:44 +00:00
2010-01-09 21:11:44 +00:00
2010-01-09 21:11:44 +00:00

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.
Description
GDB that can debug Mach-Os on Linux
Readme 280 MiB
Languages
C 58.3%
Makefile 18.5%
Assembly 13.3%
C++ 3.6%
Scheme 1.2%
Other 4.7%