This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Suggestion: backtrace stop guard for threads callstacks


On Thu, Mar 02, 2006 at 09:55:20AM -0800, Joel Brobecker wrote:
> I understand. But I also thought that it would be nice to avoid printing
> the frames that are relative to thread startup code, and start the
> backtrace at the function the code used in the pthread_create call
> for instance. I think that the user won't be interested in them most
> of the time.

Oh - actually stop the backtrace _before_ the library instead of _in_
it?

I'm not sure I agree; while the user may not be interested in the
library functions, you can call thread startup functions as normal
functions also; having backtraces stop without a clear indication
of why would be a little confusing too.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]