Package: gdb Version: 6.4.90.dfsg-1 Severity: important Hi,
I discovered this with the latest kdevelop3.4 svn version, the current gdb in debian is really slow setting breakpoints on library loading through the mi-interface. kdevelop3.4 has an option to try to set breakpoints when the app loads a shared library (for example a plugin). This is 3 times slower with debians gdb than with a 6.5 self-compiled version. On my Pentium M 1.4GHz Laptop it takes 2 minutes using 6.5-selfcompiled to start kdevelop when breakpoints are active and 6 minutes with debians gdb. I'm sorry I have no idea if this is due to the debian-patches, the differences between 6.4.90 and 6.5 or some compilation flags. I also couldn't test yet wether this happens with cmdline-invocation of gdb, because I have no idea how to load a list of breakpoints with that and tell him to try to set them each time a shared lib is loaded... Andreas -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages gdb depends on: ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libncurses5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-1 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]
