Second quarter 2005 Archives by date
Starting: Fri Apr 1 04:38:00 GMT 2005
Ending: Thu Jun 30 09:18:00 GMT 2005
Messages: 129
- gdb/1903: internal-error: could not find partial DIE in cache
warudkar@comcast.net
- build/1904: make fails with "ada-lex.c missing and flex not available."
paul.holder@veritas.com
- gdb/1903: internal-error: could not find partial DIE in cache
Daniel Jacobowitz
- remote/1836: Memory access error while loading section xxx
Ivan Djelic
- remote/1836: Memory access error while loading section xxx
Daniel Jacobowitz
- corefiles/1905: Is SPARC 64 bit supported?
David.Pickett@phlx.com
- corefiles/1905: Is SPARC 64 bit supported?
Daniel Jacobowitz
- shlibs/1906: runtime LD_LIBRARY_PATH not read
hubert.degaudenzi@cern.ch
- shlibs/1906: runtime LD_LIBRARY_PATH not read
Daniel Jacobowitz
- corefiles/1905: Is SPARC 64 bit supported?
Pickett, David
- corefiles/1905: Is SPARC 64 bit supported?
'Daniel Jacobowitz'
- corefiles/1905: Is SPARC 64 bit supported?
Pickett, David
- corefiles/1905: Is SPARC 64 bit supported?
'Daniel Jacobowitz'
- corefiles/1905: Is SPARC 64 bit supported?
Pickett, David
- java/1907: gdb does not notice when a Java native library is loaded via classmap.db
greenrd@greenrd.org
- gdb/1908: potential security problem
solar@gentoo.org
- breakpoints/1909: Assertion failure in insert_step_resume_breakpoint_at_sal.
dgraham@nortelnetworks.com
- pending/1910: gdb does not notice when a Java native library is loaded via classmap.db
Andrew Haley
- pending/1911: gdb does not notice when a Java native library is loaded via classmap.db
Andrew Haley
- java/1907: gdb does not notice when a Java native library is loaded via classmap.db
Andrew Haley
- pending/1910: gdb does not notice when a Java native library is loaded via classmap.db
drow@sources.redhat.com
- pending/1911: gdb does not notice when a Java native library is loaded via classmap.db
drow@sources.redhat.com
- pending/1912: Re: gdb does not notice when a Java native library is loaded via classmap.db
Robin Green
- java/1907: gdb does not notice when a Java native library is loaded via classmap.db
Robin Green
- pending/1912: Re: gdb does not notice when a Java native library is loaded via classmap.db
drow@sources.redhat.com
- build/1913: Problem with build on hp-ux
f6xamf802@sneakemail.com
- shlibs/1914: gdb does not notice dynamic library loads when attached to running process
greenrd@greenrd.org
- breakpoints/1915: gdb offers to set a pending breakpoint even when it will never be able to resolve the breakpoint
greenrd@greenrd.org
- shlibs/1916: gdb does not notice dynamic library loads when attached to running process
greenrd@greenrd.org
- shlibs/1916: gdb does not notice dynamic library loads when attached to running process
drow@sources.redhat.com
- shlibs/1914: gdb does not notice dynamic library loads when attached to running process
Daniel Jacobowitz
- fortran/3: gdb segfaults associated with FORTRAN (g77) array arguments
Fred Krogh
- breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
greenrd@greenrd.org
- breakpoints/1917: Setting pending breakpoints is not scriptable, at least not intuitively
Daniel Jacobowitz
- java/1919: print calls the wrong method in a class in a shared library
greenrd@greenrd.org
- breakpoints/1918: Setting pending breakpoints is not scriptable, at least not intuitively
greenrd@greenrd.org
- breakpoints/1918: Setting pending breakpoints is not scriptable, at least not intuitively
drow@sources.redhat.com
- java/1921: print calls the wrong method in a class in a shared library
greenrd@greenrd.org
- breakpoints/1920: Setting pending breakpoints is not scriptable, at least not intuitively
greenrd@greenrd.org
- breakpoints/1920: Setting pending breakpoints is not scriptable, at least not intuitively
drow@sources.redhat.com
- gdb/1922: `gdb -p' fails on FreeBSD unless procfs is mounted
das@FreeBSD.ORG
- gdb/1922: `gdb -p' fails on FreeBSD unless procfs is mounted
Paul Gilliam
- sim/1923: Segmentation fault on x86-64 on simulated program load with arm-none-eabi-run
julian@codesourcery.com
- gdb/1922: `gdb -p' fails on FreeBSD unless procfs is mounted
David Schultz
- gdb/1924: numerous spelling errors
Jay.Kulpinski@gd-ais.com
- c++/1925: HP 11.11
jz5oo@yahoo.com
- gdb/1716: next command does not work on mips-linux-gnu platform
John Van Horne
- c++/1925: HP 11.11
Daniel Jacobowitz
- exp/1926: Info registers command produces no output for "standard register names"
fnf@specifixinc.com
- c++/1927: gdb 6.3 can't resolve overloaded functions
rrh@cray.com
- gdb/1922
kettenis@sourceware.org
- gdb/1922: `gdb -p' fails on FreeBSD unless procfs is mounted
Mark Kettenis
- threads/1928: on SuSE 9.3, gdb doesn't see multiple threads
psimanyi@terasystems.com
- c++/1929: Breapoints in class constructors do not work
jrliggett@cox.net
- gdb/1930: GDB manual uses man section notation
jimb@redhat.com
- build/1931: Build of gdb 6.2.1 on solaris 10 fails
nrao@legato.com
- gdb/1932: dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
nrao@legato.com
- gdb/1932: dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
Daniel Jacobowitz
- gdb/1933: When calling a function from gdb, unexpected SIGTRAPs are received
prw@ceiriog1.demon.co.uk
- gdb/1922
kettenis@sourceware.org
- gdb/1922: `gdb -p' fails on FreeBSD unless procfs is mounted
kettenis@gnu.org
- gdb/1930: GDB manual uses man section notation
Eli Zaretskii
- gdb/1933: When calling a function from gdb, unexpected SIGTRAPs are received
Daniel Jacobowitz
- gdb/1933: When calling a function from gdb, unexpected SIGTRAPs are received
urs.hunkeler@epfl.ch
- cli/1934: Valid floating point numbers are printed as NaN
andrew@psas.pdx.edu
- gdb/1935: Gdb aborts if set solib-search-path is called after core file is loaded
prw@ceiriog1.demon.co.uk
- gdb/1933: When calling a function from gdb, unexpected SIGTRAPs are received
Peter Wainwright
- c++/1936: Wrong address of struct member
c_keil@yahoo.de
- c++/1936: Wrong address of struct member
Daniel Jacobowitz
- threads/1937: gdb 6.2/3 does not properly support threads on Solaris10
drew.johnson@andrew.com
- threads/1938: gdb gives incorrect thread numbering and is unstable
pje@haystack.mit.edu
- threads/1938: gdb gives incorrect thread numbering and is unstable
Daniel Jacobowitz
- symtab/1939: gdb coredumps on -O1 compiled binary on x86_64
tigran@veritas.com
- exp/1940: print wrong struct value if no cast else correct
ejhuff@huff20may77.us
- gdb/1932: dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
Andrew B. Lundgren
- gdb/1932: dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
Andrew B. Lundgren
- build/1941: gdb 6.3 - compilation failed on Solaris 9
gdb@ostkamp.fastmail.fm
- c++/1942: can not set breakpoint in constructor
gnatsweb@spamit.net
- symtab/1943: method call with typedef'd pointer fails
mln@cray.com
- remote/1944: "load" to remote target fails with "Memory access error"
sjohnson@sakuraindustries.com
- gdb/1945: BFD: bfd_cache_lookup_worker GNU/Linux GCC C++
ted@midg3t.net
- breakpoints/1946: Pthread application got killed when hits the breakpoint
aksaluja@yahoo.com
- remote/1944: "load" to remote target fails with "Memory access error"
drow@sources.redhat.com
- breakpoints/1946: Pthread application got killed when hits the breakpoint
Daniel Jacobowitz
- symtab/1947: gdb should canonicalize symlinks when looking for .debug files
greenrd@greenrd.org
- remote/1948: remote_xfer_partial(): packet size probe fails when LENGTH and OFFSET are zero [target: avr]
j@uriah.heep.sax.de
- breakpoints/1946: Pthread application got killed when hits the breakpoint
Daniel Jacobowitz
- pending/1949: attaching to a running process then quitting leaves stale gdb processes
gnu@greglaw.net
- c++/1950: gdb segment fault with core dumped
chenyongbao@gmail.com
- pending/1949: attaching to a running process then quitting leaves stale gdb processes
Daniel Jacobowitz
- c++/1950: gdb segment fault with core dumped
Daniel Jacobowitz
- tui/1951: gdb does not compile on Solaris with ncurses 5.4
aaronw@net.com
- build/1952: arm-elf build fails like Problem Report: 1813
oli@snr.ch
- gdb/1953: gdb fails when breakpoint hit in NPTL thread
bryanwilkerson@yahoo.com
- exp/1926: Info registers command produces no output for "standard register names"
Fred Fish
- backtrace/1760
drow@sourceware.org
- backtrace/1760: set backtrace limit broken
drow@sources.redhat.com
- exp/1954: gdb problem with typedefs
emailamit@gmail.com
- gdb/1955: gdb cannot set breakpoints in constructors, fedora3, g++
spiros@genericad.com
- build/1611: compile errors in gdb/tui/tui-command.c
Matt Selsky
- gdb/1884: arm-none-elf target sim does not run ARM executables
Flash Sheridan
- varobj/1956: argc is always 0
kernel-stuff@comcast.net
- varobj/1956: argc is always 0
Daniel Jacobowitz
- gdb/1957: gcc arm sim fails to build with gcc 4.0 on mac osx
jjhellst@gmail.com
- backtrace/1958: bad trace on x86_64, (32bit mode), linux 2.6 and shared libs
wwc@lns.mit.edu
- sim/1959: ARMulator hangs running executable with wrong ABI
flash@pobox.com
- pending/1949: attaching to a running process then quitting leaves stale gdb processes
Greg Law
- c++/1193: g++ 3.2 creates multiple constructors: gdb 5.3 can't set breakpoints
Woody LaRue
- c++/1091: Constructor breakpoints ignored
Woody LaRue
- pending/1949: attaching to a running process then quitting leaves stale gdb processes
Daniel Jacobowitz
- c++/1960: can't use typeid
grover@kuchera.com
- testsuite/1961: Pls add a test for command input of "-("
ejhuff@huff20may77.us
- c++/1960: can't use typeid
Grover, Alan
- fortran/1530: segmentation fault for FOTRAN77 arrays
woodzltc@sources.redhat.com
- fortran/1531: segmentation fault for FOTRAN77 arrays
woodzltc@sources.redhat.com
- fortran/1531: segmentation fault for FOTRAN77 arrays
woodzltc@sources.redhat.com
- fortran/3: gdb segfaults associated with FORTRAN (g77) array arguments
woodzltc@sources.redhat.com
- fortran/1536: gdb 6.0 works with programs compiled with g77 but not HP's f77 HP-UX 11.0
woodzltc@sources.redhat.com
- fortran/1768: Seg fault with large programs?
woodzltc@sources.redhat.com
- fortran/1768: Seg fault with large programs?
woodzltc@sources.redhat.com
- fortran/1880: display of part of an array
woodzltc@sources.redhat.com
- fortran/1880: display of part of an array
Fred Krogh
- fortran/1531: segmentation fault for FOTRAN77 arrays
woodzltc@sources.redhat.com
- fortran/1531: segmentation fault for FOTRAN77 arrays (fwd)
Wu Zhou
- fortran/1880: display of part of an array (fwd)
Wu Zhou
- fortran/3: gdb segfaults associated with FORTRAN (g77) array arguments
Ralph Smith
- fortran/3: gdb segfaults associated with FORTRAN (g77) array arguments
woodzltc@sources.redhat.com
- fortran/1880: display of part of an array
Wu Zhou
- breakpoints/1915: gdb offers to set a pending breakpoint even when it will never be able to resolve the breakpoint
Ramana Radhakrishnan
Last message date:
Thu Jun 30 09:18:00 GMT 2005
Archived on: Sun Mar 8 13:17:57 GMT 2020
This archive was generated by
Pipermail 0.09 (Mailman edition).