From: George Anzinger <george@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
Pavel Machek <pavel@suse.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
Matt Mackall <mpm@selenic.com>,
discuss@x86-64.org, Daniel Jacobowitz <drow@mvista.com>
Subject: Re: KGDB 2.0.3 with fixes and development in ethernet interface
Date: Thu, 22 Jan 2004 14:54:55 -0800 [thread overview]
Message-ID: <401054BF.2080701@mvista.com> (raw)
In-Reply-To: <20040122172035.GI15271@stop.crashing.org>
Tom Rini wrote:
> On Thu, Jan 22, 2004 at 10:39:14AM +0530, Amit S. Kale wrote:
>
>>On Thursday 22 Jan 2004 4:30 am, George Anzinger wrote:
>>
>>>Amit S. Kale wrote:
>>>
>>>>Now back to gdb problem of not being able to locate registers.
>>>>schedule results in code of this form:
>>>>
>>>>schedule:
>>>>framesetup
>>>>registers save
>>>>...
>>>>...
>>>>save registers
>>>>change esp
>>>>call switchto
>>>>restore registers
>>>>...
>>>
>>>I have not analyzed this as yet. However, it does seem to me to be the
>>>same problem as trying to bt through an interrupt frame. The correct way
>>>to do this is to build the dwarf frame descriptors. I have done this for
>>>the interrupt frame and intend to send said patch out in a day or so.
>>
>>Great! I had to do it this ackward way:
>>
>>i386 ->
>
> [snip]
>
>>I guess your patch will fix this problem for i386 only. Any ideas on doing it
>>for powerpc too?
>
>
> Maybe I'm missing something, but aside from having to re-write the
> solution in PPC asm, if it's in i386 asm, why wouldn't this work for PPC
> as well?
>
I think the asm is not the issue. the only stuff used is constant and pointer
generation code, no machine instructions. All that would have to be done is to
describe, in the dwarft language, the interrupt frame. This is different for
different archs so this is where the work would be needed.
Daniel has suggested that we could just use the new bin tools where in the gas
program will build the call frames. I am not sure it can handle expressions,
however. And they are needed if you want to tie off the frame if the next step
is user land.
By the way, I don't try to build a blow by blow of the frame. Rather I assume
it is only of interest at those points where calls are made out of the interrupt
/trap code. (Or, in some cases, jumps are made back into it.)
--
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-01-22 22:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 12:29 KGDB 2.0.3 with fixes and development in ethernet interface Amit S. Kale
2004-01-16 12:58 ` Pavel Machek
2004-01-16 14:07 ` Christoph Hellwig
2004-01-16 14:24 ` Amit S. Kale
2004-01-16 14:17 ` Amit S. Kale
2004-01-16 14:45 ` Pavel Machek
2004-01-16 13:05 ` [discuss] " Andi Kleen
2004-01-16 14:21 ` Amit S. Kale
2004-01-16 14:45 ` Pavel Machek
2004-01-16 15:12 ` Amit S. Kale
2004-01-16 14:47 ` Pavel Machek
2004-01-16 15:15 ` Amit S. Kale
2004-01-16 15:52 ` Pavel Machek
2004-01-17 6:27 ` KGDB documentation [Re: [discuss] KGDB 2.0.3 with fixes and development in ethernet interface] Amit S. Kale
2004-01-17 9:00 ` George Anzinger
2004-01-16 18:39 ` [discuss] KGDB 2.0.3 with fixes and development in ethernet interface Matt Mackall
2004-01-16 16:13 ` Pavel Machek
2004-01-16 20:48 ` George Anzinger
2004-01-16 21:51 ` Pavel Machek
2004-01-17 1:23 ` George Anzinger
2004-01-17 9:29 ` Amit S. Kale
2004-01-17 19:54 ` George Anzinger
2004-01-21 13:46 ` Amit S. Kale
2004-01-21 18:39 ` Daniel Jacobowitz
2004-01-21 23:14 ` George Anzinger
2004-01-22 5:49 ` Amit S. Kale
2004-01-22 20:33 ` Daniel Jacobowitz
2004-01-21 23:00 ` George Anzinger
2004-01-22 5:09 ` Amit S. Kale
2004-01-22 17:20 ` Tom Rini
2004-01-22 22:54 ` George Anzinger [this message]
2004-01-22 22:57 ` Daniel Jacobowitz
2004-01-23 19:10 ` Tom Rini
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=401054BF.2080701@mvista.com \
--to=george@mvista.com \
--cc=amitkale@emsyssoft.com \
--cc=discuss@x86-64.org \
--cc=drow@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox