https://bugzilla.novell.com/show_bug.cgi?id=212223 Summary: Some functionally in GDB 6.5 was broken with recent SUSE patches Product: SUSE Linux 10.1 Version: Final Platform: PowerPC-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: dirk.hessing@novell.com QAContact: qa@suse.de CC: Patrick.Hartman@de.ibm.com Following isues were identified by SAP/IBM in gdb-6.5-9.src.rpm from http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/sr... After installing the above debugger, watchpoints work correctly with this release, but apparently SuSE added some patches that break some things. These patches are added by SuSE: 620 Aug 24 14:17 add-symbol-file-command.diff 381 Jan 23 2006 gdb-misc.patch 3391 Aug 25 11:44 gnu-hash.diff 2692 Jan 23 2006 gstack.patch 3392 May 26 22:46 loader_break.diff 1326 Jun 2 13:36 lr-frame-offset.diff 529 May 22 13:21 mst-solib-trampoline.diff 20762 Apr 23 18:22 pie-relocate.diff 2225 May 22 14:47 ppc-dwarf2-cfi.patch 589 May 31 14:35 ppc-long-double.diff 542 Jul 16 20:52 ppc64-fdesc.diff 303 May 8 16:53 readline-5.1-random.patch 2370 Jan 23 2006 readnever.patch 738 Aug 11 14:32 solib-extract-address.diff 22635 May 8 17:10 warn.patch According to SAP the following things are broken: 1. symbols in shared libraries are not displayed in the stack backtrace 2. stack frames are displayed twice (phantom frames) 3. when settings breakpoints in C++ methods, eg. by "break 'MyClass::myMethod()' ", then "info breakpoints" will show the wrong source file. The following workarounds were found by SAP: 1. At start time gdb sets a breakpoint in _dl_debug_state() to gather information about all loaded shared libs. However, it seems that gdb misses this function by 0xe970 bytes. So SAP added the ++ marked line to the patch loader_break.diff : + /* Convert 'sym_addr' from a function pointer to an address. */ + sym_addr = gdbarch_convert_from_func_ptr_addr (current_gdbarch, + sym_addr, + tmp_bfd_target); ++ sym_addr += 0xe970; + } 2. do not apply the patch ppc-dwarf2-cfi.patch 3. no workaround yet. The assumption is that this is related to problem (1) ---uname output--- Linux ld9502 2.6.16.21-0.8-ppc64 #1 SMP Mon Jul 3 18:25:39 UTC 2006 ppc64 ppc64 ppc64 GNU/Linux Machine Type = p570 lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install gdb-6.5 from the SuSE source rpm gdb-6.5-9.src.rpm on a SLES10 ppc box. 2. debug any program with a certain complexity, eg. which has multiple source files, C++ classes/methods and utilizes shared libraries. 3. set breakpoints, do "info breakpoints" and "bt". 4. Look for missing C++ symbols, wrong source files and phantom frames 5. repeat 1-3 with the described workarounds, and there should not be phantom frames and missing C++ symbols ---GDB - Power Component Data--- Userspace tool common name: gdb The userspace tool has the following bit modes: 64-bit Userspace rpm: gdb-6.5-9.src.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.