aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2016-11-30Automatic date update in version.inGDB Administrator1-1/+1
2016-11-29Automatic date update in version.inGDB Administrator1-1/+1
2016-11-28Automatic date update in version.inGDB Administrator1-1/+1
2016-11-27Automatic date update in version.inGDB Administrator1-1/+1
2016-11-26Automatic date update in version.inGDB Administrator1-1/+1
2016-11-25Automatic date update in version.inGDB Administrator1-1/+1
2016-11-24Automatic date update in version.inGDB Administrator1-1/+1
2016-11-23Automatic date update in version.inGDB Administrator1-1/+1
2016-11-22Automatic date update in version.inGDB Administrator1-1/+1
2016-11-21Automatic date update in version.inGDB Administrator1-1/+1
2016-11-20Automatic date update in version.inGDB Administrator1-1/+1
2016-11-19Automatic date update in version.inGDB Administrator1-1/+1
2016-11-18Automatic date update in version.inGDB Administrator1-1/+1
2016-11-17Automatic date update in version.inGDB Administrator1-1/+1
2016-11-16Automatic date update in version.inGDB Administrator1-1/+1
2016-11-15Automatic date update in version.inGDB Administrator1-1/+1
2016-11-14Automatic date update in version.inGDB Administrator1-1/+1
2016-11-13Automatic date update in version.inGDB Administrator1-1/+1
2016-11-12sim: mips: add PR info to ChangeLogMike Frysinger1-0/+2
2016-11-12Automatic date update in version.inGDB Administrator1-1/+1
2016-11-11sim: mips: fix dv-tx3904cpu build errorMike Frysinger2-0/+10
When building for mipstx39-rtems4.12 targets, some funcs use SD and CPU implicitly. Restore the defines for these to the local sd and cpu vars. This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb. Reported-by: Joel Sherrill <joel.sherrill@oarcorp.com>
2016-11-11sim: mips: fix builds for r3900 cpus due to missing check_u64Mike Frysinger2-0/+5
2016-11-11Automatic date update in version.inGDB Administrator1-1/+1
2016-11-10Automatic date update in version.inGDB Administrator1-1/+1
2016-11-09Automatic date update in version.inGDB Administrator1-1/+1
2016-11-08Automatic date update in version.inGDB Administrator1-1/+1
2016-11-07Automatic date update in version.inGDB Administrator1-1/+1
2016-11-06Automatic date update in version.inGDB Administrator1-1/+1
2016-11-05Automatic date update in version.inGDB Administrator1-1/+1
2016-11-04Automatic date update in version.inGDB Administrator1-1/+1
2016-11-03Automatic date update in version.inGDB Administrator1-1/+1
2016-11-02Automatic date update in version.inGDB Administrator1-1/+1
2016-11-01Automatic date update in version.inGDB Administrator1-1/+1
2016-10-31Automatic date update in version.inGDB Administrator1-1/+1
2016-10-30Automatic date update in version.inGDB Administrator1-1/+1
2016-10-29Automatic date update in version.inGDB Administrator1-1/+1
2016-10-28Automatic date update in version.inGDB Administrator1-1/+1
2016-10-27Automatic date update in version.inGDB Administrator1-1/+1
2016-10-26Automatic date update in version.inGDB Administrator1-1/+1
2016-10-25Added forgotten gdb/ChangeLog entry.Rainer Orth1-0/+35
2016-10-25Fix gdb C++ compilation on Solaris (PR build/20712)Rainer Orth4-68/+93
gdb 7.12 doesn't compile as C++ (tried with g++ 4.9) on Solaris (tried 10 and 12, sparc and x86). The following patch (relative to the 7.12 release, though I expect most if not all issues to be present on trunk, too) fixes this. Only a few of the changes bear explanation: * Initially, compilation failed whereever defs.h. was included: In file included from /vol/src/gnu/gdb/gdb-7.12/gdb/gdb.c:19:0: /vol/src/gnu/gdb/gdb-7.12/gdb/defs.h:630:33: error: 'double atof(const char*)' conflicts with a previous declaration extern double atof (const char *); /* X3.159-1989 4.10.1.1 */ ^ In file included from /usr/include/stdlib.h:17:0, from build-gnulib/import/stdlib.h:36, from /vol/src/gnu/gdb/gdb-7.12/gdb/common/common-defs.h:32, from /vol/src/gnu/gdb/gdb-7.12/gdb/defs.h:28, from /vol/src/gnu/gdb/gdb-7.12/gdb/gdb.c:19: /vol/gcc-4.9/lib/gcc/i386-pc-solaris2.10/4.9.0/include-fixed/iso/stdlib_iso.h:119:15: note: previous declaration 'double std::atof(const char*)' extern double atof(const char *); ^ This is due to this gem in gdb/defs.h which seems to have been present like forever: #ifndef atof extern double atof (const char *); /* X3.159-1989 4.10.1.1 */ #endif In the Solaris headers, the appropriate functions are in namespace std, thus the conflict. I've wrapped the defs.h declaration in !__cplusplus to avoid this; perhaps it can go completely instead. * All the casts are necessary to appease g++ and should be pretty obvious. * The sol-thread.c changes are here to handle /vol/src/gnu/gdb/gdb-7.12/gdb/sol-thread.c: In function 'void _initialize_sol_thread()': /vol/src/gnu/gdb/gdb-7.12/gdb/sol-thread.c:1252:36: error: invalid conversion from 'void*' to 'void (*)(int)' [-fpermissive] if (!(p_##X = dlsym (dlhandle, #X))) \ ^ /vol/src/gnu/gdb/gdb-7.12/gdb/sol-thread.c:1255:3: note: in expansion of macro 'resolve' resolve (td_log); ^ and are modeled after linux-thread-db.c (try_thread_db_load_1). The patch allowed both 32 and 64-bit C++ builds on sparc-sun-solaris2.10 and i386-pc-solaris2.10 to complete. The resulting binary hasn't seen more than a smoke test (invoke it on itself, b main, run) yet. When investigating the failure to detect -static-libstdc++ support (more below), I found two more issues which only show up with -Werror: /vol/src/gnu/gdb/gdb/local/gdb/procfs.c: In function 'ssd* proc_get_LDT_entry(procinfo*, int)': /vol/src/gnu/gdb/gdb/local/gdb/procfs.c:2487:19: error: variable 'old_chain' set but not used [-Werror=unused-but-set-variable] struct cleanup *old_chain = NULL; ^ Unless I'm mistaken, you need to run do_cleanups on every return from the function. Afterwards, I ran a 32-bit compilation, which (after adding --disable-largefile to avoid In file included from /usr/include/sys/procfs.h:28:0, from /vol/src/gnu/gdb/gdb/local/gdb/i386-sol2-nat.c:23: /usr/include/sys/old_procfs.h:39:2: error: #error "Cannot use procfs in the large file compilation environment" #error "Cannot use procfs in the large file compilation environment" ^ and two more instances) revealed /vol/src/gnu/gdb/gdb/local/gdb/top.c: In function 'void gdb_safe_append_history()': /vol/src/gnu/gdb/gdb/local/gdb/top.c:1170:59: error: format '%d' expects argument of type 'int', but argument 3 has type 'pid_t {aka long int}' [-Werror=format=] = xstrprintf ("%s-gdb%d~", history_filename, getpid ()); ^ Fixed by casting pid_t to long and printing it as such.
2016-10-25Automatic date update in version.inGDB Administrator1-1/+1
2016-10-24PR gdb/20653 - small cleanup in string_to_explicit_locationTom Tromey2-1/+6
This bug points out that string_to_explicit_location compares a char* against '\0'; whereas comparing against NULL is more normal. 2016-10-24 Tom Tromey <tom@tromey.com> PR breakpoints/20653: * location.c (string_to_explicit_location): Use NULL, not '\0'.
2016-10-24[GDBserver] Fix conversion warningYao Qi2-1/+7
I got the following warning if I build GDBserver for aarch64_be-linux-gnu, git/gdb/gdbserver/linux-aarch64-low.c:1539:39: error: invalid conversion from 'void*' to 'uint32_t* {aka unsigned int*}' [-fpermissive] uint32_t *le_buf = xmalloc (byte_len); ^ The patch is to fix the warning. gdb/gdbserver: 2016-10-24 Yao Qi <yao.qi@linaro.org> PR server/20733 * linux-aarch64-low.c (append_insns): Cast the return value to 'uint32_t *'.
2016-10-24Automatic date update in version.inGDB Administrator1-1/+1
2016-10-23Automatic date update in version.inGDB Administrator1-1/+1
2016-10-22Automatic date update in version.inGDB Administrator1-1/+1
2016-10-21Automatic date update in version.inGDB Administrator1-1/+1
2016-10-20Automatic date update in version.inGDB Administrator1-1/+1
2016-10-19Automatic date update in version.inGDB Administrator1-1/+1