On Tue, Jul 10, 2007 at 01:45:32AM +0200, Wouter Verhelst wrote: > 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.
Could you show me the output of such a session, please? -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
