On Fri, Aug 08, 2008 at 04:07:28PM -0300, Wouter Verhelst wrote: > 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.
GDB doesn't differentiate between library and application functions; I assume this is some difference in the PLT sequence between applications and shared libraries that GDB is not prepared for. -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
