From: George Anzinger <george@mvista.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
linux-kernel@vger.kernel.org, trini@kernel.crashing.org,
pavel@ucw.cz
Subject: Re: kgdb for mainline kernel: core-lite [patch 1/3]
Date: Mon, 08 Mar 2004 14:21:44 -0800 [thread overview]
Message-ID: <404CF1F8.1030207@mvista.com> (raw)
In-Reply-To: <20040308034838.2ce64732.akpm@osdl.org>
Andrew Morton wrote:
> "Amit S. Kale" <amitkale@emsyssoft.com> wrote:
>
>>>Let me just make sure we're taking about the same thing here. Are you
>>>saying that with kgdb-lite, `info threads' is completely missing, or does
>>>it just not work correctly with threads (as opposed to heavyweight
>>>processes)?
>>
>>info threads shows a list of threads. Heavy/light weight processes doesn't
>>matter. Thread frame shown is incorrect.
>
>
> It is? I haven't noticed any problems with it here. George recently
> changed it to also display the process name in the gdb output, which is
> valuable.
>
>
>>I looked at i386 dependent code again. Following code in it is incorrect. I
>>never noticed it because this code is rarely used in full version of kgdb:
>>
>>+void sleeping_thread_to_gdb_regs(unsigned long *gdb_regs, struct task_struct
>>*p)
>
>
> There is no such function in the stub in -mm kernels.
>
>
>>Present threads support code changes calling convention of do_IRQ. Most
>>believe that to be an absolute no.
>
>
> I see no such change in George's stub, unless I'm missing something again.
Amit and I went after the problem in rather different ways...
>
>
>>Since you consider it a must-have, I'll check whether above changes suggested
>>by me make info threads listing correct in most cases.
>
>
> The only problem I have with it is that sometimes after listing all threads
> the debugger can lose control of the target and will start complaining
> about communication errors. I assume the target has died. This happens
> very rarely. Usually when you're about to find the bug ;)
Yeah, you won't believe how much work it took to detect that ;)
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-03-08 22:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 9:39 kgdb for mainline kernel: core-lite [patch 1/3] Amit S. Kale
2004-03-08 9:54 ` Andrew Morton
2004-03-08 10:15 ` Amit S. Kale
2004-03-08 10:26 ` Andrew Morton
2004-03-08 10:49 ` Amit S. Kale
2004-03-08 11:07 ` Andrew Morton
2004-03-08 11:20 ` Amit S. Kale
2004-03-08 11:44 ` Amit S. Kale
2004-03-08 11:54 ` Andrew Morton
2004-03-08 12:00 ` Amit S. Kale
2004-03-08 15:19 ` Tom Rini
2004-03-08 22:26 ` George Anzinger
2004-03-09 8:58 ` Amit S. Kale
2004-03-08 22:19 ` George Anzinger
2004-03-09 5:08 ` Amit S. Kale
2004-03-09 15:37 ` Tom Rini
2004-03-08 11:48 ` Andrew Morton
2004-03-08 22:21 ` George Anzinger [this message]
2004-03-08 15:22 ` Tom Rini
2004-03-08 16:32 ` Amit S. Kale
2004-03-08 22:29 ` George Anzinger
2004-03-08 22:15 ` George Anzinger
2004-03-09 4:46 ` Amit S. Kale
2004-03-09 9:29 ` Amit S. Kale
2004-03-09 9:32 ` i386-lite [patch 2/3] [Re: kgdb for mainline kernel: core-lite [patch 1/3]] Amit S. Kale
2004-03-09 15:06 ` kgdb for mainline kernel: core-lite [patch 1/3] Tom Rini
2004-03-10 4:05 ` Amit S. Kale
[not found] <1xpyM-2Op-21@gated-at.bofh.it>
[not found] ` <1xqXN-44F-13@gated-at.bofh.it>
[not found] ` <1xr7w-4c4-9@gated-at.bofh.it>
[not found] ` <1xrqW-4rh-51@gated-at.bofh.it>
[not found] ` <1xuS8-83Q-11@gated-at.bofh.it>
2004-03-08 16:57 ` Andi Kleen
2004-03-08 17:18 ` Tom Rini
2004-03-09 4:29 ` Amit S. Kale
2004-03-09 4:36 ` Amit S. Kale
2004-03-10 12:36 ` Andi Kleen
2004-03-10 15:27 ` Tom Rini
2004-03-11 4:57 ` Amit S. Kale
2004-03-11 5:05 ` Randy.Dunlap
2004-03-11 5:11 ` Andi Kleen
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=404CF1F8.1030207@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=amitkale@emsyssoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.