GitXplorerGitXplorer
S

debian-gdb

public
0 stars
0 forks
0 issues

Commits

List of commits on branch experimental.
Unverified
72725df3cdfc131502d945c7c15840243c49c3bf

Configure gdb-multiarch with --enable-64-bit-bfd so it supports 64-bit

SSamB committed 12 years ago
Unverified
92aeb9b5795b988656747d783c8be506646f8b5c

Poor man's merge of 7.4.1+dfsg-0.1.

SSamB committed 12 years ago
Unverified
3d6a24920f32a1c56ea1a3fc103df7d8a66e54f3

Oops: update patches to actually apply & don't claim to both update & drop gdbinit-ownership.patch...

SSamB committed 12 years ago
Unverified
78a581b9dc17748a6399c60bba4bcaf4b54c243e

Close #595179 (gdb64: dangling man page symlink).

SSamB committed 12 years ago
Unverified
7557d9c46f8ab735d6d035c71856db1bd2f7692c

Drop gdbinit-ownership.patch; upstream fixed CVE-2005-1705 differently.

SSamB committed 12 years ago
Unverified
722f37376acc0cd9a5c57bb0aeeca6561b887404

Merge branch 'master' into experimental

SSamB committed 12 years ago

README

The README file for this repository.
	   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.