Package: gdb Version: 6.6.dfsg-1 Severity: important Hi,
Since fairly recently, gdb on powerpc in sid misbehaves when a function call to a shared library is being executed. Rather than just stepping into the function (or skipping it if 'next' is being used), gdb first steps into a function called 'call___do_global_ctors_aux()'. After going through this function, a number of things may happen: in some cases it jumps to yet another function before actually going through the function that has been requested; after that, the request to skip over the actual function when 'next' has been used may or may not be totally ignored. In some cases even the return from the function call is not caught anymore, so that the program simply continues running from that point on, rather than allowing me to step through the code. This makes properly debugging programs rather hard. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.21-2-powerpc Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gdb depends on: ii libc6 2.6-1 GNU C Library: Shared libraries ii libncurses5 5.6-3 Shared libraries for terminal hand ii libreadline5 5.2-3 GNU readline and history libraries gdb recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
