NameDateSize

..06-Nov-201227

abug-rom.c06-Nov-20126 KiB

acinclude.m406-Nov-201230.1 KiB

aclocal.m406-Nov-201231.3 KiB

ada-exp.c06-Nov-201281.3 KiB

ada-exp.y06-Nov-201227 KiB

ada-lang.c06-Nov-2012228.2 KiB

ada-lang.h06-Nov-201210.3 KiB

ada-lex.l06-Nov-201222.6 KiB

ada-tasks.c06-Nov-201220.4 KiB

ada-typeprint.c06-Nov-201222.9 KiB

ada-valprint.c06-Nov-201226.2 KiB

alpha-mdebug-tdep.c06-Nov-201211.5 KiB

alpha-nat.c06-Nov-20127.6 KiB

alpha-tdep.c06-Nov-201247.8 KiB

alpha-tdep.h06-Nov-20124.8 KiB

alphabsd-nat.c06-Nov-20123.8 KiB

alphabsd-tdep.c06-Nov-20121.7 KiB

alphabsd-tdep.h06-Nov-20121.2 KiB

alphafbsd-tdep.c06-Nov-20123.5 KiB

alphanbsd-tdep.c06-Nov-20126.6 KiB

amd64-nat.c06-Nov-20124.8 KiB

amd64-nat.h06-Nov-20121.9 KiB

amd64-tdep.c06-Nov-201234.1 KiB

amd64-tdep.h06-Nov-20123 KiB

amd64bsd-nat.c06-Nov-20123.1 KiB

amd64fbsd-nat.c29-Nov-20136.2 KiB

amd64fbsd-tdep.c06-Nov-20124.1 KiB

amd64nbsd-nat.c06-Nov-20122 KiB

amd64nbsd-tdep.c06-Nov-20123.8 KiB

amd64obsd-nat.c06-Nov-20122 KiB

amd64obsd-tdep.c06-Nov-20125.8 KiB

annotate.c06-Nov-201211 KiB

annotate.h06-Nov-20123.9 KiB

arch-utils.c06-Nov-201220.3 KiB

arch-utils.h06-Nov-20126.2 KiB

arm-tdep.c20-Apr-201688.1 KiB

arm-tdep.h06-Nov-20125.5 KiB

armnbsd-nat.c06-Nov-201210.7 KiB

armnbsd-tdep.c06-Nov-20123.1 KiB

auxv.c06-Nov-20128.6 KiB

auxv.h06-Nov-20122.8 KiB

ax-gdb.c06-Nov-201258.5 KiB

ax-gdb.h06-Nov-20124.5 KiB

ax-general.c06-Nov-201214.5 KiB

ax.h06-Nov-201210.1 KiB

bcache.c06-Nov-201212.9 KiB

bcache.h06-Nov-20126.7 KiB

bfd-target.c06-Nov-20123.6 KiB

bfd-target.h06-Nov-20121.3 KiB

block.c06-Nov-20128 KiB

block.h06-Nov-20125.5 KiB

blockframe.c06-Nov-201220.2 KiB

breakpoint.c06-Nov-2012233.4 KiB

breakpoint.h06-Nov-201229.3 KiB

buildsym.c06-Nov-201232.4 KiB

buildsym.h06-Nov-20128 KiB

c-exp.c06-Nov-2012101.3 KiB

c-exp.y06-Nov-201248.8 KiB

c-lang.c06-Nov-201221.8 KiB

c-lang.h06-Nov-20122.7 KiB

c-typeprint.c06-Nov-201234.4 KiB

c-valprint.c19-May-201517.8 KiB

call-cmds.h06-Nov-20121.4 KiB

charset.c06-Nov-201244.6 KiB

charset.h06-Nov-20124.5 KiB

cli/12-Sep-201916

cli-out.c06-Nov-20129.6 KiB

cli-out.h06-Nov-20121.1 KiB

coff-pe-read.c06-Nov-20129.7 KiB

coff-pe-read.h06-Nov-20121.2 KiB

coff-solib.c06-Nov-20123.2 KiB

coff-solib.h06-Nov-20126.4 KiB

coffread.c06-Nov-201262.2 KiB

command.h06-Nov-201210.6 KiB

complaints.c06-Nov-20129.4 KiB

complaints.h06-Nov-20122 KiB

completer.c06-Nov-201221.9 KiB

completer.h06-Nov-20121.4 KiB

config/18-Feb-201323

CONTRIBUTE06-Nov-20124.7 KiB

COPYING06-Nov-201217.6 KiB

copying.awk06-Nov-20122.3 KiB

copying.c06-Nov-201222.6 KiB

core-aout.c06-Nov-20124.3 KiB

core-regset.c06-Nov-20123.5 KiB

corefile.c06-Nov-201212 KiB

corelow.c27-Jan-201517.6 KiB

cp-abi.c06-Nov-20126.7 KiB

cp-abi.h06-Nov-20126.2 KiB

cp-namespace.c06-Nov-201226.9 KiB

cp-support.c06-Nov-201220.1 KiB

cp-support.h06-Nov-20123.5 KiB

cp-valprint.c16-Dec-201224.1 KiB

cpu32bug-rom.c06-Nov-20126.2 KiB

dbug-rom.c06-Nov-20126 KiB

dbxread.c06-Nov-2012113 KiB

dcache.c06-Nov-201215.3 KiB

dcache.h06-Nov-20121.3 KiB

defs.h06-Nov-201240.3 KiB

delta68-nat.c06-Nov-20122.6 KiB

demangle.c06-Nov-20127.1 KiB

dictionary.c06-Nov-201223.5 KiB

dictionary.h06-Nov-20125.5 KiB

dink32-rom.c06-Nov-20125.4 KiB

disasm.c06-Nov-201211.6 KiB

disasm.h06-Nov-20121.3 KiB

doc/06-Nov-201220

doublest.c06-Nov-201225.1 KiB

doublest.h06-Nov-20123.6 KiB

dpx2-nat.c06-Nov-20122.5 KiB

dsrec.c06-Nov-20129.2 KiB

dummy-frame.c06-Nov-201214.8 KiB

dummy-frame.h06-Nov-20123.4 KiB

dve3900-rom.c06-Nov-201227.5 KiB

dwarf2-frame.c06-Nov-201244.9 KiB

dwarf2-frame.h06-Nov-20123.2 KiB

dwarf2expr.c19-May-201517.3 KiB

dwarf2expr.h19-May-20155.4 KiB

dwarf2loc.c19-May-201517 KiB

dwarf2loc.h06-Nov-20122.3 KiB

dwarf2read.c19-May-2015229.8 KiB

dwarfread.c06-Nov-2012107.8 KiB

elfread.c06-Nov-201225.2 KiB

environ.c06-Nov-20124.6 KiB

environ.h06-Nov-20121.7 KiB

eval.c06-Nov-201269.9 KiB

event-loop.c06-Nov-201234.6 KiB

event-loop.h06-Nov-20124.2 KiB

event-top.c12-Sep-201936.5 KiB

event-top.h06-Nov-20124.9 KiB

exc_request.defs06-Nov-20121.5 KiB

exec.c06-Nov-201220.9 KiB

exec.h06-Nov-20121.2 KiB

expprint.c06-Nov-201229.4 KiB

expression.h06-Nov-201215.3 KiB

f-exp.c06-Nov-201270.2 KiB

f-exp.y06-Nov-201228.7 KiB

f-lang.c06-Nov-201226.7 KiB

f-lang.h06-Nov-20123.6 KiB

f-typeprint.c06-Nov-201211.3 KiB

f-valprint.c16-Dec-201222.5 KiB

fbsd-proc.c06-Nov-20124.6 KiB

findvar.c06-Nov-201222.8 KiB

fork-child.c06-Nov-201213.6 KiB

frame-base.c06-Nov-20124.3 KiB

frame-base.h06-Nov-20123.2 KiB

frame-unwind.c17-Jun-20133.1 KiB

frame-unwind.h06-Nov-20125.6 KiB

frame.c20-Apr-201680.8 KiB

frame.h20-Apr-201629.6 KiB

gcore.c06-Nov-201214.1 KiB

gdb-events.c06-Nov-201210.9 KiB

gdb-events.h06-Nov-20124.5 KiB

gdb-events.sh06-Nov-201214.4 KiB

gdb-stabs.h06-Nov-20123.6 KiB

gdb.106-Nov-20128.1 KiB

gdb.c06-Nov-20121.1 KiB

gdb.gdb06-Nov-20121.1 KiB

gdb.h06-Nov-20122.2 KiB

gdb_assert.h06-Nov-20122.3 KiB

gdb_curses.h06-Nov-2012983

gdb_dirent.h06-Nov-20121.3 KiB

gdb_gcore.sh06-Nov-20121.7 KiB

gdb_indent.sh06-Nov-20122 KiB

gdb_locale.h06-Nov-20121.4 KiB

gdb_mbuild.sh06-Nov-20127.6 KiB

gdb_obstack.h06-Nov-20121.4 KiB

gdb_proc_service.h06-Nov-20122.1 KiB

gdb_regex.h06-Nov-20121 KiB

gdb_stat.h06-Nov-20122.1 KiB

gdb_string.h06-Nov-20121.7 KiB

gdb_thread_db.h06-Nov-201215.5 KiB

gdb_vfork.h06-Nov-2012951

gdb_wait.h06-Nov-20123.3 KiB

gdbarch.c06-Nov-2012211.8 KiB

gdbarch.h06-Nov-2012128.9 KiB

gdbarch.sh06-Nov-201281.3 KiB

gdbcmd.h06-Nov-20123.7 KiB

gdbcore.h06-Nov-20127.1 KiB

gdbinit.in06-Nov-2012222

gdbserver/06-Nov-201223

gdbthread.h06-Nov-20125.6 KiB

gdbtypes.c22-Dec-2012105.7 KiB

gdbtypes.h22-Dec-201248.7 KiB

glibc-tdep.c06-Nov-20123.3 KiB

glibc-tdep.h06-Nov-20121 KiB

gnu-nat.c06-Nov-201296 KiB

gnu-nat.h06-Nov-20123.6 KiB

gnu-v2-abi.c06-Nov-201212.6 KiB

gnu-v3-abi.c06-Nov-201216.2 KiB

go32-nat.c06-Nov-201253.6 KiB

gregset.h06-Nov-20122.4 KiB

hpacc-abi.c06-Nov-201210.9 KiB

hpread.c22-Dec-2012208 KiB

i386-nat.c06-Nov-201221.4 KiB

i386-nto-tdep.c18-Feb-20137.6 KiB

i386-sol2-tdep.c06-Nov-20123.4 KiB

i386-stub.c06-Nov-201224.2 KiB

i386-tdep.c06-Nov-201259.4 KiB

i386-tdep.h06-Nov-20127.1 KiB

i386bsd-nat.c06-Nov-201211.7 KiB

i386bsd-tdep.c06-Nov-20124.4 KiB

i386fbsd-nat.c06-Nov-20123.4 KiB

i386fbsd-tdep.c06-Nov-20125.3 KiB

i386gnu-nat.c06-Nov-20127.8 KiB

i386gnu-tdep.c06-Nov-20121.4 KiB

i386ly-tdep.c06-Nov-20122.5 KiB

i386nbsd-tdep.c06-Nov-20127.5 KiB

i386obsd-nat.c06-Nov-20121.9 KiB

i386obsd-tdep.c06-Nov-20127.8 KiB

i386v-nat.c06-Nov-20126.6 KiB

i386v4-nat.c06-Nov-20124.6 KiB

i387-tdep.c06-Nov-201222 KiB

i387-tdep.h06-Nov-20124.4 KiB

ia64-fbsd-nat.c06-Nov-20123.9 KiB

ia64-fbsd-tdep.c06-Nov-201210.3 KiB

ia64-tdep.c06-Nov-2012102.9 KiB

ia64-tdep.h06-Nov-20121.5 KiB

inf-loop.c06-Nov-20124 KiB

inf-loop.h06-Nov-20121.2 KiB

infcall.c06-Nov-201240.9 KiB

infcall.h06-Nov-20121.5 KiB

infcmd.c06-Nov-201261.3 KiB

inferior.h06-Nov-201214.7 KiB

inflow.c06-Nov-201220.5 KiB

inflow.h06-Nov-20121.5 KiB

infptrace.c06-Nov-201218.1 KiB

infrun.c06-Nov-2012138.7 KiB

inftarg.c06-Nov-201218.3 KiB

infttrace.c06-Nov-2012141.3 KiB

infttrace.h06-Nov-20121 KiB

interps.c06-Nov-201212.8 KiB

interps.h06-Nov-20122.6 KiB

jv-exp.c06-Nov-201280.7 KiB

jv-exp.y06-Nov-201235.3 KiB

jv-lang.c06-Nov-201231.3 KiB

jv-lang.h06-Nov-20122.3 KiB

jv-typeprint.c06-Nov-20129 KiB

jv-valprint.c16-Dec-201214.3 KiB

kod-cisco.c06-Nov-20128.1 KiB

kod.c06-Nov-20126.9 KiB

kod.h06-Nov-20122.3 KiB

language.c06-Nov-201239.1 KiB

language.h06-Nov-201216.7 KiB

libunwind-frame.c06-Nov-201210.8 KiB

libunwind-frame.h06-Nov-20122 KiB

lin-lwp.c06-Nov-201251.5 KiB

linespec.c06-Nov-201255.2 KiB

linespec.h06-Nov-20121.1 KiB

lynx-nat.c06-Nov-201214.5 KiB

m2-exp.c06-Nov-201274.3 KiB

m2-exp.y06-Nov-201225.1 KiB

m2-lang.c06-Nov-201213.7 KiB

m2-lang.h06-Nov-20121.2 KiB

m2-typeprint.c06-Nov-20121.4 KiB

m2-valprint.c06-Nov-20121.5 KiB

macrocmd.c06-Nov-20128.7 KiB

macroexp.c06-Nov-201233.8 KiB

macroexp.h06-Nov-20123.8 KiB

macroscope.c06-Nov-20124.3 KiB

macroscope.h06-Nov-20122.3 KiB

macrotab.c06-Nov-201226.8 KiB

macrotab.h06-Nov-201212.7 KiB

main.c06-Nov-201226.1 KiB

main.h06-Nov-20121 KiB

maint.c06-Nov-201225.2 KiB

MAINTAINERS06-Nov-201213.8 KiB

mdebugread.c06-Nov-2012149.8 KiB

mem-break.c06-Nov-20122.8 KiB

memattr.c06-Nov-201211.7 KiB

memattr.h06-Nov-20122.6 KiB

mi/06-Nov-201222

minimon.h06-Nov-201213.4 KiB

minsyms.c06-Nov-201233.4 KiB

mips-nat.c06-Nov-20127.3 KiB

mips-tdep.c06-Nov-2012200.7 KiB

mips-tdep.h06-Nov-20122.4 KiB

mipsfbsd-nat.c06-Nov-20123.1 KiB

mipsfbsd-tdep.c06-Nov-201216 KiB

mipsfbsd-tdep.h06-Nov-20121.6 KiB

mipsnbsd-nat.c06-Nov-20122.7 KiB

mipsnbsd-tdep.c06-Nov-20129.4 KiB

mipsnbsd-tdep.h06-Nov-20121.2 KiB

mipsread.c06-Nov-201213.4 KiB

mipsv4-nat.c06-Nov-20125.4 KiB

monitor.c06-Nov-201259.5 KiB

monitor.h06-Nov-20129.4 KiB

msg.defs06-Nov-201225

msg_reply.defs06-Nov-201231

nbsd-tdep.c06-Nov-20122.7 KiB

nbsd-tdep.h06-Nov-20121.1 KiB

NEWS06-Nov-201288.9 KiB

nlmread.c06-Nov-20127.8 KiB

notify.defs06-Nov-201228

nto-procfs.c18-Feb-201334.8 KiB

nto-tdep.c18-Feb-20138.5 KiB

nto-tdep.h18-Feb-20134.6 KiB

objc-exp.c06-Nov-2012100.5 KiB

objc-exp.y06-Nov-201246.4 KiB

objc-lang.c06-Nov-201249.5 KiB

objc-lang.h06-Nov-20122.2 KiB

objfiles.c06-Nov-201225.2 KiB

objfiles.h06-Nov-201225.7 KiB

observer.c06-Nov-20126.7 KiB

observer.h06-Nov-20121.2 KiB

ocd.c06-Nov-201227.8 KiB

ocd.h06-Nov-20124.8 KiB

osabi.c13-Feb-201418.6 KiB

osabi.h06-Nov-20122.3 KiB

p-exp.c06-Nov-201282.2 KiB

p-exp.y06-Nov-201243.2 KiB

p-lang.c06-Nov-201214.8 KiB

p-lang.h06-Nov-20122.6 KiB

p-typeprint.c06-Nov-201222 KiB

p-valprint.c16-Dec-201231.5 KiB

pa64solib.c06-Nov-201238.1 KiB

pa64solib.h06-Nov-20126 KiB

parse.c22-Dec-201235.1 KiB

parser-defs.h06-Nov-20128.3 KiB

ppc-bdm.c06-Nov-201210 KiB

ppc-sysv-tdep.c06-Nov-201233.9 KiB

ppc-tdep.h06-Nov-20124.5 KiB

ppcbug-rom.c06-Nov-20127.5 KiB

ppcfbsd-nat.c06-Nov-20124.5 KiB

ppcfbsd-tdep.c01-Nov-201918.1 KiB

ppcfbsd-tdep.h06-Nov-20121.1 KiB

ppcnbsd-nat.c06-Nov-20123.3 KiB

ppcnbsd-tdep.c06-Nov-20127.3 KiB

ppcnbsd-tdep.h06-Nov-20121.1 KiB

printcmd.c06-Nov-201258.7 KiB

PROBLEMS06-Nov-20124 KiB

proc-api.c18-Feb-201324.6 KiB

proc-events.c18-Feb-201344 KiB

proc-flags.c18-Feb-20139.4 KiB

proc-service.c06-Nov-20127.7 KiB

proc-utils.h06-Nov-20123.4 KiB

proc-why.c18-Feb-20134.7 KiB

process_reply.defs06-Nov-201235

procfs.c06-Nov-2012156.2 KiB

README06-Nov-201220.6 KiB

regcache.c06-Nov-201254.3 KiB

regcache.h06-Nov-201210.4 KiB

regformats/06-Nov-201214

reggroups.c06-Nov-20127.6 KiB

reggroups.h06-Nov-20122.3 KiB

regset.h06-Nov-20121.3 KiB

remote-e7000.c06-Nov-201245.9 KiB

remote-est.c06-Nov-20126.1 KiB

remote-fileio.c06-Nov-201232 KiB

remote-fileio.h06-Nov-20121.3 KiB

remote-hms.c06-Nov-20125.7 KiB

remote-mips.c06-Nov-201296.7 KiB

remote-rdi.c06-Nov-201227.7 KiB

remote-rdp.c06-Nov-201233.2 KiB

remote-sds.c06-Nov-201225.3 KiB

remote-sim.c06-Nov-201224.2 KiB

remote-st.c06-Nov-201219.3 KiB

remote-utils.c06-Nov-201213.4 KiB

remote-utils.h06-Nov-20124.1 KiB

remote-vx.c06-Nov-201238.1 KiB

remote-vx68.c06-Nov-20124.7 KiB

remote-vxmips.c06-Nov-20126.6 KiB

remote-vxsparc.c06-Nov-20123.7 KiB

remote.c24-Jan-2015160.6 KiB

remote.h06-Nov-20122.3 KiB

reply_mig_hack.awk06-Nov-20124.1 KiB

rom68k-rom.c06-Nov-20127.2 KiB

rs6000-nat.c06-Nov-201233.7 KiB

rs6000-tdep.c06-Nov-201294.2 KiB

s390-nat.c06-Nov-20129.4 KiB

s390-tdep.c06-Nov-201292.1 KiB

s390-tdep.h06-Nov-20123.1 KiB

scm-exp.c06-Nov-20128.6 KiB

scm-lang.c06-Nov-20128 KiB

scm-lang.h06-Nov-20122.6 KiB

scm-tags.h06-Nov-201211.5 KiB

scm-valprint.c16-Dec-20129.5 KiB

sentinel-frame.c06-Nov-20123 KiB

sentinel-frame.h06-Nov-20121.5 KiB

ser-e7kpc.c06-Nov-20129.1 KiB

ser-go32.c06-Nov-201222.2 KiB

ser-pipe.c06-Nov-20124.3 KiB

ser-tcp.c06-Nov-20125.6 KiB

ser-unix.c06-Nov-201231.4 KiB

ser-unix.h06-Nov-20122.1 KiB

serial.c06-Nov-201215.5 KiB

serial.h06-Nov-20128.6 KiB

signals/06-Nov-20123

sim-regno.h06-Nov-20121.5 KiB

sol-thread.c06-Nov-201246.9 KiB

solib-legacy.c06-Nov-20125 KiB

solib-osf.c06-Nov-201217 KiB

solib-sunos.c06-Nov-201227 KiB

solib-svr4.c06-Nov-201250.2 KiB

solib-svr4.h06-Nov-20123.1 KiB

solib.c06-Nov-201225.8 KiB

solib.h06-Nov-20123.6 KiB

solist.h06-Nov-20125.1 KiB

somread.c06-Nov-201224.2 KiB

somsolib.c06-Nov-201249.2 KiB

somsolib.h06-Nov-20126.5 KiB

source.c06-Nov-201240.6 KiB

source.h06-Nov-20122.9 KiB

sparc-nat.c06-Nov-201210.1 KiB

sparc-nat.h06-Nov-20121.5 KiB

sparc-sol2-nat.c06-Nov-20123.1 KiB

sparc-sol2-tdep.c06-Nov-20126.4 KiB

sparc-stub.c06-Nov-201218.6 KiB

sparc-tdep.c06-Nov-201240.7 KiB

sparc-tdep.h06-Nov-20125.4 KiB

sparc64-nat.c06-Nov-20122.6 KiB

sparc64-sol2-tdep.c06-Nov-20125.5 KiB

sparc64-tdep.c06-Nov-201241 KiB

sparc64-tdep.h06-Nov-20123.8 KiB

sparc64fbsd-nat.c06-Nov-20121.1 KiB

sparc64fbsd-tdep.c06-Nov-20127 KiB

sparc64nbsd-nat.c06-Nov-20124.1 KiB

sparc64nbsd-tdep.c06-Nov-20127.7 KiB

sparc64obsd-tdep.c06-Nov-20125.9 KiB

sparcnbsd-nat.c06-Nov-20121.1 KiB

sparcnbsd-tdep.c06-Nov-201210.9 KiB

sparcobsd-tdep.c06-Nov-20124.8 KiB

srec.h06-Nov-20121.4 KiB

stabsread.c22-Dec-2012129.5 KiB

stabsread.h06-Nov-20126.5 KiB

stack.c16-Dec-201264.2 KiB

stack.h06-Nov-2012979

standalone.c06-Nov-201211.4 KiB

std-regs.c24-Jan-20154.9 KiB

stop-gdb.c06-Nov-20123.1 KiB

sun3-nat.c06-Nov-20125.3 KiB

symfile.c06-Nov-2012111.4 KiB

symfile.h06-Nov-201211.2 KiB

symmisc.c06-Nov-201235.3 KiB

symtab.c06-Nov-2012116.2 KiB

symtab.h06-Nov-201245.7 KiB

target.c06-Nov-201262.9 KiB

target.h06-Nov-201245.7 KiB

terminal.h06-Nov-20122.8 KiB

thread-db.c06-Nov-201236.2 KiB

thread.c06-Nov-201218.9 KiB

TODO06-Nov-20127.6 KiB

top.c12-Sep-201955.5 KiB

top.h06-Nov-20122.6 KiB

tracepoint.c12-Sep-201978.6 KiB

tracepoint.h06-Nov-20124 KiB

trad-frame.c06-Nov-20124.1 KiB

trad-frame.h06-Nov-20123.2 KiB

tui/06-Feb-201835

typeprint.c06-Nov-20129.8 KiB

typeprint.h06-Nov-20121.1 KiB

ui-file.c06-Nov-201214.8 KiB

ui-file.h06-Nov-20124 KiB

ui-out.c06-Nov-201227.2 KiB

ui-out.h06-Nov-20128.6 KiB

user-regs.c06-Nov-20126 KiB

user-regs.h06-Nov-20122.6 KiB

utils.c06-Nov-201278.8 KiB

uw-thread.c18-Feb-201328.2 KiB

valarith.c06-Nov-201237.2 KiB

valops.c06-Nov-201289 KiB

valprint.c16-Dec-201242.3 KiB

valprint.h06-Nov-20122.8 KiB

value.h19-May-201520.1 KiB

values.c19-May-201540.8 KiB

varobj.c16-Dec-201260.2 KiB

varobj.h06-Nov-20123.2 KiB

version.h06-Nov-20121.1 KiB

version.in06-Nov-20126

win32-nat.c06-Nov-201266.4 KiB

wince-stub.c06-Nov-201216.5 KiB

wince-stub.h06-Nov-20121.4 KiB

wince.c06-Nov-201255.7 KiB

wrapper.c06-Nov-20127.9 KiB

wrapper.h06-Nov-20121.8 KiB

xcoffread.c06-Nov-201285.7 KiB

xcoffsolib.c06-Nov-20125.2 KiB

xcoffsolib.h06-Nov-20122.4 KiB

xmodem.c06-Nov-20126.1 KiB

xmodem.h06-Nov-20121.3 KiB

README

1		     README for gdb-6.1 release
2		Updated 29 February, 2004 by Andrew Cagney
3
4This is GDB, the GNU source-level debugger.
5
6A summary of new features is in the file `gdb/NEWS'.
7
8Check the GDB home page at http://www.gnu.org/software/gdb/ for up to
9date release information, mailing list links and archives, etc.
10
11The file `gdb/PROBLEMS' contains information on problems identified
12late in the release cycle.  GDB's bug tracking data base at
13http://www.gnu.org/software/gdb/bugs/ contains a more complete list of
14bugs.
15
16
17Unpacking and Installation -- quick overview
18==========================
19
20   In this release, the GDB debugger sources, the generic GNU include
21files, the BFD ("binary file description") library, the readline
22library, and other libraries all have directories of their own
23underneath the gdb-6.1 directory.  The idea is that a variety of GNU
24tools can share a common copy of these things.  Be aware of variation
25over time--for example don't try to build gdb with a copy of bfd from
26a release other than the gdb release (such as a binutils release),
27especially if the releases are more than a few weeks apart.
28Configuration scripts and makefiles exist to cruise up and down this
29directory tree and automatically build all the pieces in the right
30order.
31
32   When you unpack the gdb-6.1.tar.gz file, you'll find a directory
33called `gdb-6.1', which contains:
34
35  COPYING       config.sub    intl         missing         opcodes
36  COPYING.LIB   configure     libiberty    mkinstalldirs   readline
37  Makefile.in   configure.in  libtool.m4   mmalloc         sim
38  README        djunpack.bat  ltcf-c.sh    move-if-change  symlink-tree
39  bfd           etc           ltcf-cxx.sh  mpw-README      texinfo
40  config        gdb           ltcf-gcj.sh  mpw-build.in    utils
41  config-ml.in  gettext.m4    ltconfig     mpw-config.in   ylwrap
42  config.guess  include       ltmain.sh    mpw-configure
43  config.if     install-sh    md5.sum      mpw-install
44
45You can build GDB right in the source directory:
46
47      cd gdb-6.1
48      ./configure
49      make
50      cp gdb/gdb /usr/local/bin/gdb	(or wherever you want)
51
52However, we recommend that an empty directory be used instead.
53This way you do not clutter your source tree with binary files
54and will be able to create different builds with different 
55configuration options.
56
57You can build GDB in any empty build directory:
58
59      mkdir build
60      cd build
61      <full path to your sources>/gdb-6.1/configure
62      make
63      cp gdb/gdb /usr/local/bin/gdb	(or wherever you want)
64
65(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
66different; see the file gdb-6.1/gdb/config/djgpp/README for details.)
67
68   This will configure and build all the libraries as well as GDB.  If
69`configure' can't determine your system type, specify one as its
70argument, e.g., `./configure sun4' or `./configure decstation'.
71
72   Make sure that your 'configure' line ends in 'gdb-6.1/configure':
73
74      /berman/migchain/source/gdb-6.1/configure      # RIGHT
75      /berman/migchain/source/gdb-6.1/gdb/configure  # WRONG
76
77   The gdb package contains several subdirectories, such as 'gdb',
78'bfd', and 'readline'.  If your 'configure' line ends in
79'gdb-6.1/gdb/configure', then you are configuring only the gdb
80subdirectory, not the whole gdb package.  This leads to build errors
81such as:
82
83      make: *** No rule to make target `../bfd/bfd.h', needed by `gdb.o'.  Stop.
84
85   If you get other compiler errors during this stage, see the `Reporting
86Bugs' section below; there are a few known problems.
87
88   GDB requires an ISO C (ANSI C) compiler.  If you do not have an ISO
89C compiler for your system, you may be able to download and install
90the GNU CC compiler.  It is available via anonymous FTP from the
91directory `ftp://ftp.gnu.org/pub/gnu/gcc'.
92
93   GDB can be used as a cross-debugger, running on a machine of one
94type while debugging a program running on a machine of another type.
95See below.
96
97
98More Documentation
99******************
100
101   All the documentation for GDB comes as part of the machine-readable
102distribution.  The documentation is written in Texinfo format, which
103is a documentation system that uses a single source file to produce
104both on-line information and a printed manual.  You can use one of the
105Info formatting commands to create the on-line version of the
106documentation and TeX (or `texi2roff') to typeset the printed version.
107
108   GDB includes an already formatted copy of the on-line Info version
109of this manual in the `gdb/doc' subdirectory.  The main Info file is
110`gdb-6.1/gdb/doc/gdb.info', and it refers to subordinate files
111matching `gdb.info*' in the same directory.  If necessary, you can
112print out these files, or read them with any editor; but they are
113easier to read using the `info' subsystem in GNU Emacs or the
114standalone `info' program, available as part of the GNU Texinfo
115distribution.
116
117   If you want to format these Info files yourself, you need one of the
118Info formatting programs, such as `texinfo-format-buffer' or
119`makeinfo'.
120
121   If you have `makeinfo' installed, and are in the top level GDB
122source directory (`gdb-6.1', in the case of version 6.1), you can make
123the Info file by typing:
124
125      cd gdb/doc
126      make info
127
128   If you want to typeset and print copies of this manual, you need
129TeX, a program to print its DVI output files, and `texinfo.tex', the
130Texinfo definitions file.  This file is included in the GDB
131distribution, in the directory `gdb-6.1/texinfo'.
132
133   TeX is a typesetting program; it does not print files directly, but
134produces output files called DVI files.  To print a typeset document,
135you need a program to print DVI files.  If your system has TeX
136installed, chances are it has such a program.  The precise command to
137use depends on your system; `lpr -d' is common; another (for PostScript
138devices) is `dvips'.  The DVI print command may require a file name
139without any extension or a `.dvi' extension.
140
141   TeX also requires a macro definitions file called `texinfo.tex'. 
142This file tells TeX how to typeset a document written in Texinfo
143format.  On its own, TeX cannot read, much less typeset a Texinfo file.
144 `texinfo.tex' is distributed with GDB and is located in the
145`gdb-6.1/texinfo' directory.
146
147   If you have TeX and a DVI printer program installed, you can typeset
148and print this manual.  First switch to the the `gdb' subdirectory of
149the main source directory (for example, to `gdb-6.1/gdb') and then type:
150
151      make doc/gdb.dvi
152
153   If you prefer to have the manual in PDF format, type this from the
154`gdb/doc' subdirectory of the main source directory:
155
156      make gdb.pdf
157
158For this to work, you will need the PDFTeX package to be installed.
159
160
161Installing GDB
162**************
163
164   GDB comes with a `configure' script that automates the process of
165preparing GDB for installation; you can then use `make' to build the
166`gdb' program.
167
168   The GDB distribution includes all the source code you need for GDB in
169a single directory, whose name is usually composed by appending the
170version number to `gdb'.
171
172   For example, the GDB version 6.1 distribution is in the `gdb-6.1'
173directory.  That directory contains:
174
175`gdb-6.1/{COPYING,COPYING.LIB}'
176     Standard GNU license files.  Please read them.
177
178`gdb-6.1/bfd'
179     source for the Binary File Descriptor library
180
181`gdb-6.1/config*'
182     script for configuring GDB, along with other support files
183
184`gdb-6.1/gdb'
185     the source specific to GDB itself
186
187`gdb-6.1/include'
188     GNU include files
189
190`gdb-6.1/libiberty'
191     source for the `-liberty' free software library
192
193`gdb-6.1/mmalloc'
194     source for the GNU memory-mapped malloc package
195
196`gdb-6.1/opcodes'
197     source for the library of opcode tables and disassemblers
198
199`gdb-6.1/readline'
200     source for the GNU command-line interface
201     NOTE:  The readline library is compiled for use by GDB, but will
202     not be installed on your system when "make install" is issued.
203
204`gdb-6.1/sim'
205     source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
206
207`gdb-6.1/intl'
208     source for the GNU gettext library, for internationalization.
209     This is slightly modified from the standalone gettext
210     distribution you can get from GNU.
211
212`gdb-6.1/texinfo'
213     The `texinfo.tex' file, which you need in order to make a printed
214     manual using TeX.
215
216`gdb-6.1/etc'
217     Coding standards, useful files for editing GDB, and other
218     miscellanea.
219
220`gdb-6.1/utils'
221     A grab bag of random utilities.
222
223   Note: the following instructions are for building GDB on Unix or
224Unix-like systems.  Instructions for building with DJGPP for
225MS-DOS/MS-Windows are in the file gdb/config/djgpp/README.
226
227   The simplest way to configure and build GDB is to run `configure'
228from the `gdb-VERSION-NUMBER' source directory, which in this example
229is the `gdb-6.1' directory.
230
231   First switch to the `gdb-VERSION-NUMBER' source directory if you are
232not already in it; then run `configure'.
233
234   For example:
235
236      cd gdb-6.1
237      ./configure
238      make
239
240   Running `configure' followed by `make' builds the `bfd',
241`readline', `mmalloc', and `libiberty' libraries, then `gdb' itself.
242The configured source files, and the binaries, are left in the
243corresponding source directories.
244
245   `configure' is a Bourne-shell (`/bin/sh') script; if your system
246does not recognize this automatically when you run a different shell,
247you may need to run `sh' on it explicitly:
248
249      sh configure
250
251   If you run `configure' from a directory that contains source
252directories for multiple libraries or programs, such as the `gdb-6.1'
253source directory for version 6.1, `configure' creates configuration
254files for every directory level underneath (unless you tell it not to,
255with the `--norecursion' option).
256
257   You can run the `configure' script from any of the subordinate
258directories in the GDB distribution, if you only want to configure that
259subdirectory; but be sure to specify a path to it.
260
261   For example, with version 6.1, type the following to configure only
262the `bfd' subdirectory:
263
264      cd gdb-6.1/bfd
265      ../configure
266
267   You can install `gdb' anywhere; it has no hardwired paths. However,
268you should make sure that the shell on your path (named by the `SHELL'
269environment variable) is publicly readable.  Remember that GDB uses the
270shell to start your program--some systems refuse to let GDB debug child
271processes whose programs are not readable.
272
273
274Compiling GDB in another directory
275==================================
276
277   If you want to run GDB versions for several host or target machines,
278you need a different `gdb' compiled for each combination of host and
279target.  `configure' is designed to make this easy by allowing you to
280generate each configuration in a separate subdirectory, rather than in
281the source directory.  If your `make' program handles the `VPATH'
282feature correctly (GNU `make' and SunOS 'make' are two that should),
283running `make' in each of these directories builds the `gdb' program
284specified there.
285
286   To build `gdb' in a separate directory, run `configure' with the
287`--srcdir' option to specify where to find the source. (You also need
288to specify a path to find `configure' itself from your working
289directory.  If the path to `configure' would be the same as the
290argument to `--srcdir', you can leave out the `--srcdir' option; it
291will be assumed.)
292
293   For example, with version 6.1, you can build GDB in a separate
294directory for a Sun 4 like this:
295
296     cd gdb-6.1
297     mkdir ../gdb-sun4
298     cd ../gdb-sun4
299     ../gdb-6.1/configure
300     make
301
302   When `configure' builds a configuration using a remote source
303directory, it creates a tree for the binaries with the same structure
304(and using the same names) as the tree under the source directory.  In
305the example, you'd find the Sun 4 library `libiberty.a' in the
306directory `gdb-sun4/libiberty', and GDB itself in `gdb-sun4/gdb'.
307
308   One popular reason to build several GDB configurations in separate
309directories is to configure GDB for cross-compiling (where GDB runs on
310one machine--the host--while debugging programs that run on another
311machine--the target).  You specify a cross-debugging target by giving
312the `--target=TARGET' option to `configure'.
313
314   When you run `make' to build a program or library, you must run it
315in a configured directory--whatever directory you were in when you
316called `configure' (or one of its subdirectories).
317
318   The `Makefile' that `configure' generates in each source directory
319also runs recursively.  If you type `make' in a source directory such
320as `gdb-6.1' (or in a separate configured directory configured with
321`--srcdir=PATH/gdb-6.1'), you will build all the required libraries,
322and then build GDB.
323
324   When you have multiple hosts or targets configured in separate
325directories, you can run `make' on them in parallel (for example, if
326they are NFS-mounted on each of the hosts); they will not interfere
327with each other.
328
329
330Specifying names for hosts and targets
331======================================
332
333   The specifications used for hosts and targets in the `configure'
334script are based on a three-part naming scheme, but some short
335predefined aliases are also supported.  The full naming scheme encodes
336three pieces of information in the following pattern:
337
338     ARCHITECTURE-VENDOR-OS
339
340   For example, you can use the alias `sun4' as a HOST argument or in a
341`--target=TARGET' option.  The equivalent full name is
342`sparc-sun-sunos4'.
343
344   The `configure' script accompanying GDB does not provide any query
345facility to list all supported host and target names or aliases. 
346`configure' calls the Bourne shell script `config.sub' to map
347abbreviations to full names; you can read the script, if you wish, or
348you can use it to test your guesses on abbreviations--for example:
349
350     % sh config.sub sun4
351     sparc-sun-sunos4.1.1
352     % sh config.sub sun3
353     m68k-sun-sunos4.1.1
354     % sh config.sub decstation
355     mips-dec-ultrix4.2
356     % sh config.sub hp300bsd
357     m68k-hp-bsd
358     % sh config.sub i386v
359     i386-pc-sysv
360     % sh config.sub i786v
361     Invalid configuration `i786v': machine `i786v' not recognized
362
363`config.sub' is also distributed in the GDB source directory
364(`gdb-6.1', for version 6.1).
365
366
367`configure' options
368===================
369
370   Here is a summary of the `configure' options and arguments that are
371most often useful for building GDB.  `configure' also has several other
372options not listed here.  *note : (configure.info)What Configure Does,
373for a full explanation of `configure'.
374
375     configure [--help]
376               [--prefix=DIR]
377               [--srcdir=PATH]
378               [--norecursion] [--rm]
379	       [--enable-build-warnings]
380               [--target=TARGET]
381	       [--host=HOST]
382	       [HOST]
383
384You may introduce options with a single `-' rather than `--' if you
385prefer; but you may abbreviate option names if you use `--'.
386
387`--help'
388     Display a quick summary of how to invoke `configure'.
389
390`-prefix=DIR'
391     Configure the source to install programs and files under directory
392     `DIR'.
393
394`--srcdir=PATH'
395     *Warning: using this option requires GNU `make', or another `make'
396     that compatibly implements the `VPATH' feature.*
397     Use this option to make configurations in directories separate
398     from the GDB source directories.  Among other things, you can use
399     this to build (or maintain) several configurations simultaneously,
400     in separate directories.  `configure' writes configuration
401     specific files in the current directory, but arranges for them to
402     use the source in the directory PATH.  `configure' will create
403     directories under the working directory in parallel to the source
404     directories below PATH.
405
406`--norecursion'
407     Configure only the directory level where `configure' is executed;
408     do not propagate configuration to subdirectories.
409
410`--rm'
411     Remove the configuration that the other arguments specify.
412
413`--enable-build-warnings'
414     When building the GDB sources, ask the compiler to warn about any
415     code which looks even vaguely suspicious.  You should only using
416     this feature if you're compiling with GNU CC.  It passes the
417     following flags:
418	-Wimplicit
419	-Wreturn-type
420	-Wcomment
421	-Wtrigraphs
422	-Wformat
423	-Wparentheses
424	-Wpointer-arith
425
426`--target=TARGET'
427     Configure GDB for cross-debugging programs running on the specified
428     TARGET.  Without this option, GDB is configured to debug programs
429     that run on the same machine (HOST) as GDB itself.
430
431     There is no convenient way to generate a list of all available
432     targets.
433
434`--host=HOST'
435     Configure GDB to run on the specified HOST.
436
437     There is no convenient way to generate a list of all available
438     hosts.
439
440`HOST ...'
441     Same as `--host=HOST'.  If you omit this, GDB will guess; it's
442     quite accurate.
443
444`configure' accepts other options, for compatibility with configuring
445other GNU tools recursively; but these are the only options that affect
446GDB or its supporting libraries.
447
448
449Remote debugging
450=================
451
452   The files m68k-stub.c, i386-stub.c, and sparc-stub.c are examples
453of remote stubs to be used with remote.c.  They are designed to run
454standalone on an m68k, i386, or SPARC cpu and communicate properly
455with the remote.c stub over a serial line.
456
457   The directory gdb/gdbserver/ contains `gdbserver', a program that
458allows remote debugging for Unix applications.  gdbserver is only
459supported for some native configurations, including Sun 3, Sun 4, and
460Linux.
461
462   There are a number of remote interfaces for talking to existing ROM
463monitors and other hardware:
464
465	remote-e7000.c	 Renesas E7000 ICE
466	remote-est.c	 EST emulator
467	remote-hms.c	 Renesas Micro Systems H8/300 monitor
468	remote-mips.c	 MIPS remote debugging protocol
469	remote-rdi.c	 ARM with Angel monitor
470	remote-rdp.c	 ARM with Demon monitor
471	remote-sds.c	 PowerPC SDS monitor
472	remote-sim.c	 Generalized simulator protocol
473	remote-st.c	 Tandem ST-2000 monitor
474	remote-vx.c	 VxWorks realtime kernel
475
476   Remote-vx.c and the vx-share subdirectory contain a remote
477interface for the VxWorks realtime kernel, which communicates over TCP
478using the Sun RPC library.  This would be a useful starting point for
479other remote- via-ethernet back ends.
480
481
482Reporting Bugs in GDB
483=====================
484
485   There are several ways of reporting bugs in GDB.  The prefered
486method is to use the World Wide Web:
487
488      http://www.gnu.org/software/gdb/bugs/
489
490As an alternative, the bug report can be submitted, via e-mail, to the
491address "bug-gdb@gnu.org".
492
493   When submitting a bug, please include the GDB version number (e.g.,
494gdb-6.1), and how you configured it (e.g., "sun4" or "mach386 host,
495i586-intel-synopsys target").  Since GDB now supports so many
496different configurations, it is important that you be precise about
497this.  If at all possible, you should include the actual banner that
498GDB prints when it starts up, or failing that, the actual configure
499command that you used when configuring GDB.
500
501   For more information on how/whether to report bugs, see the
502Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo).
503
504
505Graphical interface to GDB -- X Windows, MS Windows
506==========================
507
508   Several graphical interfaces to GDB are available.  You should
509check:
510
511	http://www.gnu.org/software/gdb/links/
512
513for an up-to-date list.
514
515   Emacs users will very likely enjoy the Grand Unified Debugger mode;
516try typing `M-x gdb RET'.
517
518
519Writing Code for GDB
520=====================
521
522   There is a lot of information about writing code for GDB in the
523internals manual, distributed with GDB in gdb/doc/gdbint.texinfo.  You
524can read it by hand, print it by using TeX and texinfo, or process it
525into an `info' file for use with Emacs' info mode or the standalone
526`info' program.
527
528   If you are pondering writing anything but a short patch, especially
529take note of the information about copyrights in the node Submitting
530Patches.  It can take quite a while to get all the paperwork done, so
531we encourage you to start that process as soon as you decide you are
532planning to work on something, or at least well ahead of when you
533think you will be ready to submit the patches.
534
535
536GDB Testsuite
537=============
538
539   Included with the GDB distribution is a DejaGNU based testsuite
540that can either be used to test your newly built GDB, or for
541regression testing a GDB with local modifications.
542
543   Running the testsuite requires the prior installation of DejaGNU,
544which is generally available via ftp.  The directory
545ftp://sources.redhat.com/pub/dejagnu/ will contain a recent snapshot.
546Once DejaGNU is installed, you can run the tests in one of the
547following ways:
548
549  (1)	cd gdb-6.1
550	make check-gdb
551
552or
553
554  (2)	cd gdb-6.1/gdb
555	make check
556
557or
558
559  (3)	cd gdb-6.1/gdb/testsuite
560	make site.exp	(builds the site specific file)
561	runtest -tool gdb GDB=../gdb    (or GDB=<somepath> as appropriate)
562
563The last method gives you slightly more control in case of problems
564with building one or more test executables or if you are using the
565testsuite `standalone', without it being part of the GDB source tree.
566
567See the DejaGNU documentation for further details.
568
569
570(this is for editing this file with GNU emacs)
571Local Variables:
572mode: text
573End:
574