Third quarter 2006 Archives by subject
Starting: Sun Jul 2 21:58:00 GMT 2006
Ending: Fri Sep 29 20:58:00 GMT 2006
Messages: 95
- ada/2156: infinite loop when trying to print ada array
timo.lindfors@iki.fi
- backtrace/2147: "Quit" ignored in backtrace if printing arguments
ed@catmur.co.uk
- backtrace/2157: Backtrace not working with programs build with dmd for the D-programming language.
benoit@tionex.de
- backtrace/2157: Backtrace not working with programs build with dmd for the D-programming language.
Frank Benoit
- backtrace/2157: Backtrace not working with programs build with dmd for the D-programming language.
Frank Benoit
- backtrace/2178: gdb crashes to thread_db_map_id2thr
seb128@ubuntu.com
- backtrace/2178: gdb crashes to thread_db_map_id2thr
Daniel Jacobowitz
- backtrace/2178: gdb crashes to thread_db_map_id2thr
Sebastien Bacher
- breakpoints/2119: gdb 6.4 prints errors when restarting program with pending breakpoints
Greg Law
- breakpoints/2142: debug target has incorrect remove_watchpoint implementation
petr@vmware.com
- breakpoints/2165: Stepping over longjmp presumably broken for glibc
eggert@gnu.org
- breakpoints/735: Getting the i386 watchpoints into the target vector?
Petr Vandrovec
- build/2167: make failed
hi.shibuya@vertexsystems.co.jp
- build/2167: make failed
Daniel Jacobowitz
- build/2167: make failed
drow@sources.redhat.com
- build/2175: LDFLAGS{,_FOR_TARGET} and are not saved in Makefile
mkl@pengutronix.de
- build/2176: CPPFLAGS and are not saved in Makefile
mkl@pengutronix.de
- c++/2152: set print object on does not work
cbarbe@obj-sys.com
- c++/2152: set print object on does not work
Daniel Jacobowitz
- c++/2152: set print object on does not work
Daniel Jacobowitz
- c++/2152: set print object on does not work
christophe barbe
- c++/2160: gdb segfaults on extern "C"
neeman@webone.com.au
- c++/2168: Could not find virtual table pointer when using gcc 3.2.3
larue@cadence.com
- c++/2169: cant step into more than 1 function call on a single line
intangir@gmail.com
- c++/2170: cant step into more than 1 function call on a single line
intangir@gmail.com
- c++/2177: Enum support in dwarf reader is inconsistent
drow@false.org
- c++/2179: Segmentation fault in find_overload_match
zhegulev@klocwork.com
- c++/488: vtable, RTTI, and namespaces don't work together
James Cone
- corefiles/2151: gdb useless with core files
johna@onevista.com
- corefiles/2151: gdb useless with core files
Daniel Jacobowitz
- corefiles/2151: gdb useless with core files
drow@sources.redhat.com
- exp/2150: floating-point infinity value is wrongly displayed as 0 on AMD64
gawrilow@math.tu-berlin.de
- fortran/2144: gdb crash when my code is compiled with -fcase-preserve
burlen@apollo.sr.unh.edu
- fortran/2155: Segmentation fault with passed-length character arguments
grb@tf.uni-kiel.de
- fortran/2174: PATCH: Support DW_TAG_entry_point
hjl@lucon.org
- gdb/1898: free pascal, Darwin Kernel Version 7.8.0, Power Macintosh powerpc
Jonas Maebe
- gdb/2143: gdb reports Program exited normally when it should not
matty_gardiner@yahoo.co.uk
- gdb/2145: GDB6.4 fails lots of thread related tests on SPARC
johan.walles@bea.com
- gdb/2145: GDB6.4 fails lots of thread related tests on SPARC
Johan Walles
- gdb/2146: remote_fetch_registers (int regnum) ... if (regnum >= 0) {
roland.puntaier@br-automation.com
- gdb/2146: remote_fetch_registers (int regnum) ... if (regnum >= 0) {
Daniel Jacobowitz
- gdb/2153: bad usabillity when quiting gdb + easy fix
ensonic@hora-obscura.de
- gdb/2153: bad usabillity when quiting gdb + easy fix
Daniel Jacobowitz
- gdb/2153: bad usabillity when quiting gdb + easy fix
Stefan Kost
- gdb/2162: gdb dumps core in cplus_demangle_type() while trying to demangle non-mangled identifier
dns@fortess.net
- gdb/2164: Single stepping partially broken for Solaris
gordon.prieur@sun.com
- gdb/2171: No backtrace generated on amd64
madcoder@gmail.com
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64
Joe Hansche
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64
Joe Hansche
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64
Joe Hansche
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64
Joe Hansche
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64
Daniel Jacobowitz
- gdb/2171: No backtrace generated on amd64 [SOLVED]
Joe Hansche
- gdb/2172: gdb-6.5 solaris 10 x86 i86pc 64-bit support, prerequesuites, install
alois.wiedenhofer@culturall.com
- gdb/2172: gdb-6.5 solaris 10 x86 i86pc 64-bit support, prerequesuites, install
Daniel Jacobowitz
- gdb/2172: gdb-6.5 solaris 10 x86 i86pc 64-bit support, prerequesuites, install
Alois Wiedenhofer
- gdb/2172: gdb-6.5 solaris 10 x86 i86pc 64-bit support, prerequesuites, install
Daniel Jacobowitz
- remote/1966
drow@sourceware.org
- remote/1966: trust-readonly-sections does not work
drow@sources.redhat.com
- remote/2154
drow@sourceware.org
- remote/2154: cached buffer pointers not updated after executing new getpkt
strauman@slac.stanford.edu
- remote/2154: cached buffer pointers not updated after executing new getpkt
Daniel Jacobowitz
- remote/2154: cached buffer pointers not updated after executing new getpkt
drow@sources.redhat.com
- remote/2158: Memory access error while loading section .text, Escape characters
ronald.hecht@gmx.de
- remote/2158: Memory access error while loading section .text, Escape characters
Daniel Jacobowitz
- remote/2158: Memory access error while loading section .text, Escape characters
Ronald Hecht
- remote/2158: Memory access error while loading section .text, Escape characters
Ronald Hecht
- symtab/2159: lookup_partial_symtab() inefficient
larue@cadence.com
- symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
alex00882007@gmail.com
- symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
Daniel Jacobowitz
- symtab/2161: Debug Info|ELF| GDB shows memory as being mapped when it might not be
Daniel Jacobowitz
- threads/1792: ptrace / thread_db_get_info errors when debugging rhythmbox
drow@sources.redhat.com
- threads/1872: After segfault on client app "info threads" causes gdb to segfault
Edward Catmur
- threads/1872: After segfault on client app "info threads" causes gdb to segfault
Edward Catmur
- threads/2128: suppression of new thread and thread exit messages
Torsten Rohlfing
- threads/2148: gdb can't read core dumps from crashed multi-threaded C++ programs
nkiesel@tbdnetworks.com
- threads/2148: gdb can't read core dumps from crashed multi-threaded C++ programs
Daniel Jacobowitz
- threads/2148: gdb can't read core dumps from crashed multi-threaded C++ programs
Norbert Kiesel
- threads/2149
drow@sourceware.org
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
alex@alex.org.uk
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
Matthew M. DeLoera
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
Daniel Jacobowitz
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
Matthew M. DeLoera
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
Alex Bligh
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
Alex Bligh
- threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp()
drow@sources.redhat.com
- threads/568: GDB confused by messily-exiting multi-threaded programs
drow@sources.redhat.com
- tui/2173: Arrow keys no longer works in breakpoint command list
hjl@lucon.org
- varobj/2163: Unicode string support
f18m_cpp217828@yahoo.it
- win32/2166: Unchecked file close causes SEGV
roblip@gmail.com
Last message date:
Fri Sep 29 20:58:00 GMT 2006
Archived on: Sun Mar 8 13:18:00 GMT 2020
This archive was generated by
Pipermail 0.09 (Mailman edition).