Hi, I *thought* I'd sent some more information on this bug a while ago, but apparently I didn't. Sorry about that.
This bug no longer occurs if you're only trying to debug an application; gdb understands that an application is not a library, and accordingly doesn't attempt to step into a function if the function is a library call. However, once you start stepping into a library (because, say, you're actually developing a library), the distinction between 'application functions' and 'library functions' that gdb uses to distinguish whether or not to step in or over a library call disappears (because every call is a library call, I presume), and the bug reappears. -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
