aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2013-07-03[PATCH, COMMITTED] [AArch64] Replace the :got_prel19: address modifier with ↵Marcus Shawcroft7-11/+19
:got:
2013-07-03[AArch64] Tidy up switch statement in GAS.Marcus Shawcroft2-32/+37
2013-07-03[AArch64] Tidy up switch statements in elfnn-aarch64.cMarcus Shawcroft2-30/+38
2013-07-03On mainline/development, also link GDBserver with -lmcheck.Pedro Alves12-56/+216
This factors --enable-libmcheck related bits from GDB's configure.ac and makes GDBserver use them too. Specifically, the 'development' global is moved to a separate script to it can be sourced by both GDB and GDBserver, and the --enable-libmcheck/--disable-libmcheck bits proper are moved to a new m4 file. I started out by defining 'development' in the m4 file, but in the end decided against it, as a separate script has the advantage that changing it in release branches does not require regenerating configure, unlike today. I had also started out by making the new GDB_AC_LIBMCHECK itself handle the yes/no default fallback depending on release/developement, but since I had split out 'development' to a separate script, and, GDB needs the python checks anyway (hence we'd need to do the python checks in gdb's configure.ac, and pass in a 'default lmcheck yes/no' parameter to GDB_AC_LIBMCHECK anyway), I ended up keeping GDB_AC_LIBMCHECK isolated from the 'development' global. IOW, it's the caller's business to handle it. Tested on x86_64 Fedora 17. Built GDB and GDBserver with and without --enable-libmcheck, and observed --enable-libmcheck overrides the disablement of -lmcheck caused by python supporting threads, and that GDBserver links with -lmcheck when expected. Also observed that changing the 'development' global, and issuing "make" triggers a relink, and '-lmcheck' is included or not from the link accordingly. gdb/ 2013-07-03 Pedro Alves <palves@redhat.com> * Makefile.in (config.status): Depend on development.sh. (aclocal_m4_deps): Add libmcheck.m4. * acinclude.m4: Include libmcheck.m4. * configure.ac: Source development.sh instead of setting 'development' here. --enable-libmcheck/--disable-libmcheck code factored out to GDB_AC_LIBMCHECK. Run it. * development.sh: New file. * libmcheck.m4: New file. * configure: Regenerate. gdb/gdbserver/ 2013-07-03 Pedro Alves <palves@redhat.com> * Makefile.in (config.status): Depend on development.sh. * acinclude.m4: Include libmcheck.m4. * configure: Regenerate.
2013-07-03 * elf64-ppc.c (ppc64_elf_func_desc_adjust): Don't hide .TOC.Alan Modra2-6/+10
when relocatable. Don't change root.type or type here. (ppc64_elf_set_toc): Set type of .TOC. to STT_OBJECT.
2013-07-03bfd/Alan Modra4-47/+89
* elf64-ppc.c (struct ppc_stub_hash_entry): Delete "addend". (ppc64_elf_size_stubs): Don't set "addend". (ppc64_elf_relocate_section): Don't allow calls via toc-adjusting stubs without a following nop even in an executable, except for self-calls and both libc_start_main and .libc_start_main. gold/ * powerpc.cc (Target_powerpc::Relocate::relocate): Update self-call comment.
2013-07-03 * elf64-ppc.c (ppc64_elf_func_desc_adjust): Hide ".TOC.".Alan Modra2-1/+12
2013-07-03daily updateAlan Modra1-1/+1
2013-07-02gdb/testsuite/Jan Kratochvil2-2/+10
* gdb.base/break-on-linker-gcd-function.exp: Replace prepare_for_testing by build_executable_from_specs and clean_restart.
2013-07-02 * contrib/ari/update-web-ari.sh: Update for version.in change.Tom Tromey2-1/+6
2013-07-02 * common/ptid.h: Comment fixes.Tom Tromey2-2/+6
2013-07-02remove mention of "target nrom"Tom Tromey2-10/+4
The documentation refers to "target nrom", but this target doesn't appear in the tree. It was zapped here: 2002-12-16 Andrew Cagney <ac131313@redhat.com> [...] * remote-nrom.c, remote-os9k.c, remote-vx960.c: Delete. This patch removes the reference from the documentation. * gdb.texinfo (Target Commands): Don't mention "target nrom".
2013-07-022013-07-02 Tristan Gingold <gingold@adacore.com>Tristan Gingold2-0/+6
* coff-rs6000.c (xcoff_find_nearest_line_discriminator): Add missing line.
2013-07-02gdbserver, win32: fix some function typedefsMircea Gherzan2-4/+12
2013-05-25 Mircea Gherzan <mircea.gherzan@intel.com> gdbserver/ * win32-low.c (winapi_DebugActiveProcessStop): Move the WINAPI attribute inside the parentheses. (winapi_DebugSetProcessKillOnExit): Ditto. (winapi_DebugBreakProcess): Ditto. (winapi_GenerateConsoleCtrlEvent): Ditto. Change-Id: I3aab72f2a1725a46b9da0e41a4ba08d7886284b9 Signed-off-by: Mircea Gherzan <mircea.gherzan@intel.com>
2013-07-02gdbserver: avoid empty structsMircea Gherzan2-0/+7
2013-06-25 Mircea Gherzan <mircea.gherzan@intel.com> gdbserver/ * notif.h (notif_event): Add a dummy member to avoid compiler errors. Change-Id: I490dbdb70a24f52b3947371f7c0397bf7a18423c Signed-off-by: Mircea Gherzan <mircea.gherzan@intel.com>
2013-07-022013-07-02 Tristan Gingold <gingold@adacore.com>Tristan Gingold2-0/+27
* vms-alpha.c (_bfd_generic_find_nearest_line_discriminator): Define. (_bfd_vms_find_nearest_line_discriminator): New function.
2013-07-022013-07-02 Tristan Gingold <gingold@adacore.com>Tristan Gingold2-8/+13
* coff-rs6000.c (xcoff_create_csect_from_smclas): Handle more smclas.
2013-07-022013-07-02 Tristan Gingold <gingold@adacore.com>Tristan Gingold2-1/+22
* coff-rs6000.c (xcoff_find_nearest_line_discriminator): New function. (rs6000coff_vec): Reference it.
2013-07-022013-07-02 Tristan Gingold <gingold@adacore.com>Tristan Gingold3-0/+11
* internal.h (C_STTLS, C_GTLS): Define. * xcoff.h (XMC_TL, XMC_TU, XMC_TE): Define.
2013-07-02[AArch64] Fix creation of .got and placement of _GLOBAL_OFFSET_TABLE_Marcus Shawcroft10-36/+106
2013-07-02[AArch64] Adjust testcases for move of &_DYNAMIC to got[0].Marcus Shawcroft10-15/+27
2013-07-02bfd/Alan Modra4-9/+17
* elf64-ppc.c (ppc64_elf_relocate_section): Set "relocation" for .TOC. after relocatable check. gas/ * config/tc-ppc.c (ppc_elf_adjust_symtab): Don't make .TOC. weak.
2013-07-02daily updateAlan Modra1-1/+1
2013-07-01gold/Cary Coutant3-6/+40
* dwarf_reader.cc (Dwarf_ranges_table::read_ranges_table): Save reloc_type_. (Dwarf_ranges_table::read_range_list): Call lookup_reloc. (Dwarf_ranges_table::lookup_reloc): New function. * dwarf_reader.h (Dwarf_ranges_table::Dwarf_ranges_table): Initialize reloc_type_. (Dwarf_ranges_table::lookup_reloc): New function. (Dwarf_ranges_table::reloc_type_): New data member.
2013-07-01change gdb to use BFD's "dwz" functionsTom Tromey2-22/+31
BFD recently got a few functions related to "dwz" files. This patch changes gdb to use them, just to share a bit more code. This changes dwarf2_get_dwz_file to possibly return NULL. This simplified a bit of code elsewhere. Built and regtested on x86-64 Fedora 18. I specifically regtested it using my pending dwz test case. * dwarf2read.c (dwarf2_get_dwz_file): Return NULL if .gnu_debugaltlink not found. Use bfd_get_alt_debug_link_info. (dwarf2_read_index, create_all_comp_units): Update.
2013-07-01add -Wold-style-definitionTom Tromey5-4/+13
This adds -Wold-style-definition to gdb's list of warnings. This found a couple of spots where "()" was used where "(void)" is more correct. Tested by rebuilding on x86-64 Fedora 18. * configure.ac (build_warnings): Add -Wold-style-definition. * configure: Rebuild. * machoread.c (_initialize_machoread): Use "(void)". * macrocmd.c (macro_inform_no_debuginfo): Fix formatting; use "(void)".
2013-07-01add -Wold-style-declarationTom Tromey11-16/+39
This adds -Wold-style-declaration to gdb's list of warnings. It turns out that a few places use "const static" rather than "static const". The former is deprecated according to the C standard. Tested by rebuilding with --enable-targets=all on x86-64 Fedora 18. * configure.ac (build_warnings): Add -Wold-style-declaration. * configure: Rebuild. * dsrec.c (make_srec): Use "static const", not "const static". * h8300-tdep.c (h8300_breakpoint_from_pc): Use "static const", not "const static". * mi/mi-parse.c (mi_no_values, mi_simple_values, mi_all_values): Use "static const", not "const static". * mn10300-tdep.c (mn10300_breakpoint_from_pc): Use "static const", not "const static". * moxie-tdep.c (moxie_breakpoint_from_pc): Use "static const", not "const static". * rs6000-tdep.c (rs6000_breakpoint_from_pc): Use "static const", not "const static". * v850-tdep.c (v850_breakpoint_from_pc): Use "static const", not "const static". (v850_dbtrap_breakpoint_from_pc): Likewise. * xstormy16-tdep.c (xstormy16_breakpoint_from_pc): Use "static const", not "const static".
2013-07-01add -Wmissing-parameter-typeTom Tromey3-2/+7
This adds -Wmissing-parameter-type to gdb's list of warnings. This one doesn't happen to trigger for a --enable-targets=all build on x86-64 Fedora 18. * configure.ac (build_warnings): Add -Wmissing-parameter-type. * configure: Rebuild.
2013-07-01Adjust ld-x86-64/tlsg.sdH.J. Lu2-1/+5
* ld-x86-64/tlsg.sd: Adjusted.
2013-07-01[GDBserver] hostio.c: Fallback to packet buffer size if PATH_MAX is not ↵Pedro Alves2-4/+18
available. PATH_MAX is not defined on systems which have no limit on filename length, such as GNU/Hurd. As designed, the hostio RSP packets carry the paths as parameters in the request/reply packets, which themselves have an upper size limit, so lifting the filename limit completely would require a redesign with new hostio packets. While that doesn't happen, we can at least support filename lengths as long as the packet buffer can fit. gdb/gdbserver/ 2013-07-01 Pedro Alves <palves@redhat.com> * hostio.c (HOSTIO_PATH_MAX): Define. (require_filename, handle_open, handle_unlink, handle_readlink): Use it.
2013-07-01Normalize on PATH_MAX instead of MAXPATHLEN throughout.Pedro Alves26-59/+72
With the pathmax gnulib module in place, we can use PATH_MAX consistently throughout, instead of the current mixbag of PATH_MAX and MAXPATHLEN uses. It's no longer necessary to include sys/param.h (supposedly, I can't check all ports touched here) for MAXPATHLEN. Don't remove sys/param.h from GDB's configure.ac, as later tests in the file use HAVE_SYS_PARAM_H checks. Tested on x86_64 Fedora 17. Also cross-built for --host=i686-w64-mingw32, and --host=i586-pc-msdosdjgpp. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * defs.h: Include "pathmax.h". * utils.c: Don't include sys/param.h. (gdb_realpath): Remove code that checks for MAXPATHLEN. * solib-ia64-hpux.c (ia64_hpux_handle_load_event): Use PATH_MAX instead of MAXPATHLEN. * solib-sunos.c: Don't include sys/param.h. * xcoffread.c: Don't include sys/param.h. * bsd-kvm.c: Don't include sys/param.h. * darwin-nat.c: Don't include sys/param.h. (darwin_pid_to_exec_file): Use PATH_MAX instead of MAXPATHLEN. * darwin-nat-info.c: Don't include sys/param.h. * fbsd-nat.c (fbsd_pid_to_exec_file): Use PATH_MAX instead of MAXPATHLEN. * i386obsd-nat.c: Don't include sys/param.h. * inf-child.c: Don't include sys/param.h. (inf_child_fileio_readlink): Use PATH_MAX instead of MAXPATHLEN. * linux-fork.c: Don't include sys/param.h. (fork_save_infrun_state): Use PATH_MAX instead of MAXPATHLEN. * linux-nat.c: Don't include sys/param.h. (linux_child_pid_to_exec_file, linux_proc_pending_signals) (linux_proc_pending_signals): Use PATH_MAX instead of MAXPATHLEN. * m68klinux-nat.c: Don't include sys/param.h. * nbsd-nat.c: Don't include sys/param.h. (nbsd_pid_to_exec_file): Use PATH_MAX instead of MAXPATHLEN. * ppc-linux-nat.c: Don't include sys/param.h. * rs6000-nat.c: Don't include sys/param.h. * spu-linux-nat.c. Don't include sys/param.h. * windows-nat.c: Don't include sys/param.h. * xtensa-linux-nat.c: Don't include sys/param.h. * config/i386/nm-fbsd.h: Don't include sys/param.h. gdb/gdbserver/ 2013-07-01 Pedro Alves <palves@redhat.com> * server.h: Include "pathmax.h". * linux-low.c: Don't include sys/param.h. (linux_pid_exe_is_elf_64_file): Use PATH_MAX instead of MAXPATHLEN. * win32-low.c: Don't include sys/param.h. (win32_create_inferior): Use PATH_MAX instead of MAXPATHLEN.
2013-07-01Import the "pathmax" gnulib module.Pedro Alves12-5/+169
This imports the "pathmax" gnulib module, making PATH_MAX always available on systems that have the notion of a constant max path limit (i.e., practically everywhere except the Hurd), along with fixing a couple broken systems --- see pathmax.h in the patch. This means we can normalize on PATH_MAX throughout the tree (instead of some places using MAXPATHLEN, or defining fallback constants ourselves). This is the just the importing step. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add pathmax. * gnulib/Makefile.in (aclocal_m4_deps): Add import/m4/pathmax.m4. * gnulib/aclocal.m4: Regenerate. * gnulib/config.in: Regenerate. * gnulib/configure: Regenerate. * gnulib/import/pathmax.h: New file. * gnulib/import/Makefile.am: Regenerate. * gnulib/import/Makefile.in: Regenerate. * gnulib/import/m4/gnulib-cache.m4: Regenerate. * gnulib/import/m4/gnulib-comp.m4: Regenerate. * gnulib/import/m4/pathmax.m4: New file.
2013-07-01Reimplement DJGPP's .gdbinit -> gdb.ini renaming.Pedro Alves7-17/+42
This simplifies the .gdbinit filename selection logic. We have a GDBINIT_FILENAME define that supposedly configurations would override, but none do so. Instead, the only configuration that wants a different file name instead of ".gdbinit", djgpp, does a strcpy over the gdbinit global array. This means the array needs to be sized, and the code that does that is doing the usual 'PATH_MAX/FILENAME_MAX/fallback constant/etc.' mess. Instead of all that, it's much simpler to have configure specificy the .gdbinit filename. As bonus, we can then make the "gdbinit" global array const. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * configure.ac (GDBINIT): Define, depending on host. * go32-nat.c (init_go32_ops): Don't override gdbinit here. * top.c (PATH_MAX): Delete fallback definition. (GDBINIT_FILENAME): Delete. (gdbinit): Reimplement as const char array set to the GDBINIT string constant. * top.h (gdbinit): Make const.
2013-07-01Constify main.c:get_init_files.Pedro Alves6-21/+58
A following patch will want to make the "gdbinit" global array const. As usual, that forces in a cascading series of const additions. This patch preemptively does those. I went all the way up to constifying catch_command_errors, but then that would require constifying execute_command as well (which is a much more significant effort). So as stop point, I found the cleanest would be to add a variant of catch_command_errors that takes const args, and use that in the few spots that needed it due to the the get_init_files constification. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * cli/cli-cmds.c (source_script): Make 'file' parameter const. * cli/cli-cmds.h (source_script): Likewise. * exceptions.c (catch_command_errors_const): New function. * exceptions.h (catch_command_errors_const): Declare. * main.c (get_init_files): Make parameters const, and adjust. (captured_main): Make 'system_gdbinit', 'home_gdbinit' and 'local_gdbinit' locals const. Adjust to use catch_command_errors_const. (print_gdb_help): Make 'system_gdbinit', 'home_gdbinit' and 'local_gdbinit' locals const.
2013-07-01Rely on gnulib's unistd.h replacement.Pedro Alves10-26/+19
With gnulib's unistd module, we can assume unistd.h is always present, and that STDIN_FILENO, STDOUT_FILENO, STDERR_FILENO are always defined. Don't remove unistd.h from GDB's configure.ac, as later tests in the file use HAVE_UNISTD_H checks. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * defs.h: Don't check HAVE_UNISTD_H before including <unistd.h>. (STDIN_FILENO, STDOUT_FILENO, STDERR_FILENO): Delete. * tracepoint.c: Don't check HAVE_UNISTD_H before including <unistd.h>. gdb/gdbserver/ 2013-07-01 Pedro Alves <palves@redhat.com> * event-loop.c: Don't check HAVE_UNISTD_H before including <unistd.h>. * gdbreplay.c: Likewise. * remote-utils.c: Likewise. * server.c: Likewise. * configure.ac: Don't check for unistd.h. * configure: Regenerate.
2013-07-01Import the "unistd" gnulib module.Pedro Alves17-56/+3091
I wanted to import the pathmax module, and that pulls in the unistd module as dependency. The unistd module is actually bigger than the pathmax module. If we're going to end up with it, might as well import it explicitly, and make use of it throughout. The "unistd" module makes a GNU-like <unistd.h> always available. This means we no longer need to do: +#ifdef HAVE_UNISTD_H #include <unistd.h> +#endif and we can remove a few constants from defs.h. This is just the importing step. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> Import the "unistd" gnulib module. * gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add "unistd". * gnulib/Makefile.in (aclocal_m4_deps): Add import/m4/off_t.m4, import/m4/ssize_t.m4, import/m4/sys_types_h.m4 and import/m4/unistd_h.m4. * gnulib/aclocal.m4: Renenerate. * gnulib/config.in: Renenerate. * gnulib/configure: Renenerate. * gnulib/import/Makefile.am: Renenerate. * gnulib/import/Makefile.in: Renenerate. * gnulib/import/m4/gnulib-cache.m4: Renenerate. * gnulib/import/m4/gnulib-comp.m4: Renenerate. * gnulib/import/m4/off_t.m4: New file. * gnulib/import/m4/ssize_t.m4: New file. * gnulib/import/m4/sys_types_h.m4: New file. * gnulib/import/m4/unistd_h.m4: New file. * gnulib/import/sys_types.in.h: New file. * gnulib/import/unistd.c: New file. * gnulib/import/unistd.in.h: New file.
2013-07-01utils.c: pathconf call, check for _PC_PATH_MAX instead of HAVE_UNISTD_H.Pedro Alves2-1/+6
This check in utils.c for HAVE_UNISTD_H is being used as proxy for "HAVE_PATHCONF", as pathconf is supposed to be declared in unistd.h. It's possible that there are systems out there that have realpath, unistd.h and alloca, but not pathconf+_PC_PATH_MAX. I don't know of any by heart, but if we import gnulib's unistd module (which a following patch will do), then unistd.h ends up always available, so the check ends up incorrect. As pathconf is being called with _PC_PATH_MAX, check for that instead. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * utils.c <pathconf/_PC_PATH_MAX use>: Check if _PC_PATH_MAX is defined instead of checking HAVE_UNISTD_H.
2013-07-01Reimport gnulib from scratch.Pedro Alves7-442/+56
Moving aside gnulib/import/, and re-running our gnulib/update-gnulib.sh script, surprisingly, one gets a different result compared to what's in the tree. This is with pristine FSF autoconf and FSF automake, at the versions required by update-gnulib.sh. However, if one just runs the update-gnulib.sh scripts against the _existing_ tree, then nothing changes... I suspect gnulib-tool's merge logic might be preserving some things by design. This gets rid of cruft that might have accumulated over gnulib updates. onceonly.m4 seems to fit in that category. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> Reimport gnulib from scratch. * gnulib/Makefile.in (aclocal_m4_deps): Remove reference to import/m4/onceonly.m4. * gnulib/aclocal.m4: Renegerate. * gnulib/config.in: Renegerate. * gnulib/configure: Renegerate. * gnulib/import/Makefile.in: Renegerate. * gnulib/import/extra/update-copyright: Renegerate. * gnulib/import/m4/onceonly.m4: Delete.
2013-07-01Delete pagination_enabled extern declaration in tui/tui-regs.c.Pedro Alves2-2/+4
It's declared in utils.h. gdb/ 2013-07-01 Pedro Alves <palves@redhat.com> * tui/tui-regs.c (pagination_enabled): Delete declaration.
2013-07-01bfd/Alan Modra5-20/+57
* elf64-ppc.h (ppc64_elf_toc): Delete. (ppc64_elf_set_toc): Declare. * elf64-ppc.c (ppc64_elf_toc_reloc): Replace call to ppc64_elf_toc with call the ppc64_elf_set_toc. (ppc64_elf_toc_ha_reloc, ppc64_elf_toc64_reloc): Likewise. (ppc64_elf_start_multitoc_partition): Likewise. (struct ppc_link_hash_table): Delete dot_toc_dot. Replace all uses with elf.hgot. (ppc64_elf_process_dot_syms): Don't make a fake function descriptor for ".TOC.". (ppc64_elf_check_relocs): Mark sections with a reference to .TOC. as needing a toc pointer. (ppc64_elf_size_stubs): Don't set dot_toc_dot here. (ppc64_elf_set_toc): Rename from ppc64_elf_toc. Add info param. Set elf.hgot value. ld/ * emultempl/ppc64elf.em: (ppc_layout_sections_again): Call ppc64_elf_set_toc rather than ppc64_elf_toc/_bfd_set_gp_value. (gld${EMULATION_NAME}_after_allocation): Likewise.
2013-07-01daily updateAlan Modra1-1/+1
2013-06-30gdb/Jan Kratochvil3-4/+8
Code cleanup. * remote.c (async_remote_interrupt_twice): Make it static. * remote.h (async_remote_interrupt_twice): Remove the declaration.
2013-06-30This patch implements the support for SystemTap SDT probes on IA-64.Sergio Durigan Junior2-0/+27
Joel Brobecker reported a bug which was happening because of the "Improved linker-debugger interface", by Gary Benson, when tested on IA-64 with rhES5. The message is: <http://sourceware.org/ml/gdb-patches/2013-06/msg00745.html> The failure happened because GDB was trying to parse the probes' operands using only the generic parser (implemented on stap-probe.c), because the arch-specific parser was not implemented. Thus, I am committing the following changes which solve the bug. 2013-06-29 Sergio Durigan Junior <sergiodj@redhat.com> * ia64-linux-tdep.c: Include <ctype.h>. (ia64_linux_stap_is_single_operand): New function. (ia64_linux_init_abi): Initialize SystemTap related attributes.
2013-06-30daily updateAlan Modra1-1/+1
2013-06-29daily updateAlan Modra1-1/+1
2013-06-28move version.in from gdb/common back to gdbTom Tromey14-25/+56
This reverts part of the earlier version.in change. It moves version.in back to the gdb directory. This works around the CVS bug we've found. gdb * Makefile.in (version.c): Use version.in, not common/version.in. * common/create-version.sh: Likewise. * common/version.in: Move... * version.in: ...here. gdb/doc * Makefile.in (version.subst): Use version.in, not common/version.in. * gdbint.texinfo (Versions and Branches, Releasing GDB): Likewise. gdb/gdbserver * Makefile.in (version.c): Use version.in, not common/version.in. sim/common * Make-common.in (version.c): Use version.in, not common/version.in. * create-version.sh: Likewise. sim/ppc: * Make-common.in (version.c): Use version.in, not common/version.in.
2013-06-28Move pagination_enabled declaration to a proper place.Pedro Alves3-2/+8
Declare it close to other related declarations in utils.h, and remove local extern declaration hack. gdb/ 2013-06-28 Pedro Alves <palves@redhat.com> * infrun.c (set_observer_mode): Don't declare pagination_enabled here. * utils.h (pagination_enabled): Declare.
2013-06-28infrun.c: Move non_stop_1 etc., higher up in file.Pedro Alves2-28/+32
The "non_stop_1" global is out of place, mixed with the observer bits. This moves all the non-stop user-interface-related bits together. gdb/ 2013-06-28 Pedro Alves <palves@redhat.com> * infrun.c (non_stop, non_stop_1, set_non_stop, show_non_stop): Move higher up in file.
2013-06-28Handle R_X86_64_DTPOFF64H.J. Lu5-1/+19
bfd/ PR ld/15685 * elf64-x86-64.c (elf_x86_64_relocate_section): Handle R_X86_64_DTPOFF64. ld/testsuite/ PR ld/15685 * ld-x86-64/tlsg.s: Add a test for R_X86_64_DTPOFF64. * ld-x86-64/tlsg.sd: Updated.
2013-06-28 * tracepoint.c (deprecated_readline_begin_hook)Tom Tromey2-4/+6
(deprecated_readline_hook, deprecated_readline_end_hook): Don't declare.
generated by cgit v1.1 at 2025-01-03 03:14:02 +0000