From: Andrew Cagney <cagney@gnu.org>
To: jim.houston@comcast.net
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] thread info - automatic skip frames
Date: Tue, 09 Mar 2004 20:30:00 -0000 [thread overview]
Message-ID: <404E294D.90601@gnu.org> (raw)
Message-ID: <20040309203000._oB_uzjuZSxrAvEcceNTYp5V6DS1LTtwiSD60Yj6R08@z> (raw)
In-Reply-To: <m3wu5vp5cg.fsf@new.localdomain>
> Hi Everyone,
>
> I developed this patch to support using kgdb on the
> x86-64 linux kernel.
>
> The patch adds an option to gdb to skip over boring frames
> in the "thread info" results. This is useful when most of
> the threads are stopped in the context switch code. It lets
> you see the frame which shows why the the thread blocked.
>
> Use:
> set skip-frame thread_return,schedule_timeout
I think the first thing to do is see this thread:
http://sources.redhat.com/ml/gdb/2004-03/msg00019.html
through to resolution. At present it isn't clear that the changes are
needed.
Andrew
next prev parent reply other threads:[~2004-03-09 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:23 Jim Houston
2004-03-08 23:10 ` Michael Snyder
2004-03-09 6:09 ` Eli Zaretskii
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Michael Snyder
2004-03-19 0:09 ` Jim Houston
2004-03-19 0:09 ` Andrew Cagney [this message]
2004-03-09 20:30 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=404E294D.90601@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jim.houston@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox