First quarter 2008 Archives by thread
Starting: Wed Jan 2 03:48:00 GMT 2008
Ending: Mon Mar 31 12:17:00 GMT 2008
Messages: 123
- mi/2398: newline after stream-record
generatorglukoff@gmail.com
- gdb/2399: [gdb-mingw] 'attach' command hangs
bodzio131@op.pl
- breakpoints/2400: gdb can't set breakpoints in ADA code and outputs "No source file" found
chris.sid@online.de
- mi/2309: Internal error (Assertion failure) on "-var-update" command
Nick Roberts
- threads/2395: "info stack" works, but "stack-info-depth" fails
Øyvind Harboe
- build/2401: sys/procfs.h "Present But Cannot Be Compiled"
tom@software6.net
- exp/2403: 32-bit addresses miscalculated on 64-bit platform.
mostrows@gmail.com
- exp/2402: x86-32 address calculations on x86-64 are incorrect
mostrows@gmail.com
- build/2404: gdb 6.7.1 fails to build with gcc-4.2.2 on aix 5.2
T.Mittelstaedt@cadenas.de
- build/2405: gdb 6.7.1 fails to build with gcc-4.2.2 on aix 5.2
T.Mittelstaedt@cadenas.de
- gdb/2406: avr gdb accessing ram instead of eeprom
tomas.vanek@fbl.cz
- exp/2407: Incomplete type evaluated incorrectly
oder@eleks.lviv.ua
- exp/2409: (void(**)()) is syntax error
gin@mo.msk.ru
- exp/2408: (void(**)())
gin@mo.msk.ru
- threads/2383: internal-error: linux_nat_wait: Assertion `iterate_over_lwps (running_callback, NULL)' failed.
Atsushi Nemoto
- build/2410: Missing -lintl in sim/ppc
tr@oxlug.org
- gdb/2411: documentation bug in 'info' command
tromey@redhat.com
- c++/2412: gdb crashes with complex data
jacob@jacob.remcomp.fr
- symtab/2413: If a file is Compiled as .o first and .out finally, with -g option, GDB reports (no debugging symbols found), however dbx works fine with the same file. Further if the file is compiled in single go from .cpp to .out gdb reports no such error
kumar.sumit@hotmail.com
- gdb/2345: GDB 6.7 - ptype $pc or whatis $pc causes internal-error: register_type
Bob Chapman
- mi/2414: examine data via gdb/MI fails
ullrich.martini@gi-de.com
- c++/2415: variable validation
nick78@hotbox.ru
- mi/2414: examine data via gdb/MI fails - Solved
Ullrich Martini
- c++/2416: casting to reference type causes internal error
aristovski@qnx.com
- c++/2417: Breakpoints ignored in constructors outside class {} definition
gordon.prieur@sun.com
- build/2418: build error from compiler warning for -Werror
robert.bu@gmail.com
- build/2419: build error from compiler warning for -Werror
robert.bu@gmail.com
- gdb/2420: gdb SEGV with detach-on-follow=off
tromey@redhat.com
- gdb/2421: followed child breaks in _dl_debug_state
tromey@redhat.com
- gdb/2422: detach-on-fork=off forgets parent process
tromey@redhat.com
- gdb/2423: gdb documentation index variable entries are not ideal
tromey@redhat.com
- mi/2424: When stopped at temporary breakpoint, mi-message not correct
aristovski@qnx.com
- gdb/2425: When stopped at temporary breakpoint, thread-id = 0
aristovski@qnx.com
- gdb/2426: Temporary breakpoint for "finish" command not cleaned up in MI mode
tom.fowler@hotmail.co.uk
- breakpoints/2428: add a way to toggle breakpoint 'silent' status
tromey@redhat.com
- breakpoints/2427: let "commands" select more than one breakpoint
tromey@redhat.com
- cli/1709: gdb --args no longer works
tromey@redhat.com
- gdb/2330: makeinfo version check fails for version>=4.10
tromey@redhat.com
- build/2377: Compilation error: ../gdb/tui/tui-command.c:26: tui/tui-data.h:38: syntax error before "WINDOW"
tromey@redhat.com
- gdb/1840: Have readline 5.0 would like GDB to use the 5.0 version and not the included 4.3
tromey@redhat.com
- breakpoints/1879: .gdbinit parsing error
tromey@redhat.com
- build/2367: Wrong path to config.intl in sim/ppc/configure
tromey@redhat.com
- gdb/2362: Building 6.7.1 on NetBSD 3.1 fails with compile error.
tromey@redhat.com
- build/2361: gdb 6.7 solib-irix.c: implicit declaration `solib_add'
tromey@redhat.com
- sim/2348: Incorrect gcc invocation in "sim/ppc"
tromey@redhat.com
- gdb/2162: gdb dumps core in cplus_demangle_type() while trying to demangle non-mangled identifier
tromey@redhat.com
- build/2126: make error, gdb 6.4, on IRIX 6.5.28f
tromey@redhat.com
- breakpoints/2120: "info break" output not good when cond is a function call with string arg
Tom Tromey
- build/2114: gdb-6.4 build fails at "tui-data.h:40: error: syntax error before "WINDOW""
tromey@redhat.com
- build/2095: gdb$(EXEEXT) target needs to depend and link in $(SUBDIR_MI_OBS)
tromey@redhat.com
- build/2050: remote-utils.c build error: variable declared after statement
tromey@redhat.com
- build/2049: Compilation error: gdb/tui/tui-data.h:40: syntax error before "WINDOW"
tromey@redhat.com
- gdb/2034: gdb does not compile with gcc-4.0
tromey@redhat.com
- build/1611: compile errors in gdb/tui/tui-command.c
tromey@redhat.com
- cli/1380: try/catch commands
tromey@redhat.com
- gdb/2429: gdb crashes while debugging xemacs
T.Mittelstaedt@cadenas.de
- breakpoints/2430: assembler file with multiple sections which is not adjacent can't step
jianghongjiang@gmail.com
- breakpoints/2431: function call on command line terminates with SIGTRAP
dicks@altium.nl
- gdb/1207: gdb final link fails due to missing -lintl
drow@sources.redhat.com
- backtrace/2432: gdb does not produce correct backtrace on linux mips
maxim.kozlovsky@onstor.com
- cli/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
drow@sources.redhat.com
- gdb/2433: gdb creates debuginfo path incorrectly for symlinked files
schommer@us.ibm.com
- c++/2434: C++, breakpoint set in ancestor's virtual method, for RVCT compiled elf-file
anders.hessel@enea.com
- c++/2435: gdb crash when printing an instanced class name
jlevine@cadence.com
- c++/2436: Bogus "warning: can't find linker symbol for virtual table for 'Foo' value" messages
vz-gdb@zeitlins.org
- gdb/2439: GDB 6.3/6.4 Not recognizing Core Files: GDB can't read core files on this machine.
ashishg2dec@gmail.com
- gdb/2437: GDB 6.3/6.4 Not recognizing Core Files: GDB can't read core files on this machine.
ashishg2dec@gmail.com
- gdb/2438: GDB 6.3/6.4 Not recognizing Core Files: GDB can't read core files on this machine.
ashishg2dec@gmail.com
Last message date:
Mon Mar 31 12:17:00 GMT 2008
Archived on: Sun Mar 8 13:18:04 GMT 2020
This archive was generated by
Pipermail 0.09 (Mailman edition).