From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: George Anzinger <george@mvista.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
kernel list <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [Kgdb-bugreport] [PATCH][2/3] Update CVS KGDB's have kgdb_{schedule,process}_breakpoint
Date: Mon, 15 Mar 2004 16:50:34 +0530 [thread overview]
Message-ID: <200403151650.34115.amitkale@emsyssoft.com> (raw)
In-Reply-To: <40516EDA.5060006@mvista.com>
On Friday 12 Mar 2004 1:33 pm, George Anzinger wrote:
> Amit S. Kale wrote:
> > On Friday 12 Mar 2004 2:58 am, George Anzinger wrote:
> >>Amit S. Kale wrote:
> >>~
> >>
> >>>>context any
> >>>>
> >>>>p fun()
> >>>
> >>>p fun() will push arguments on stack over the place where irq occured,
> >>>which is exactly how it'll run.
> >>
> >>Is this capability in kgdb lite? It was one of the last things I added
> >> to -mm version.
> >
> > No! It's not present in kgdb heavy also. All you can do is set $pc,
> > continue.
>
> Possibly I can help here. I did it for the mm version. It does require a
> couple of asm bits and it sort of messes up the set/fetch memory, but it
> does do the job.
I have seen that. It's too messy!
-Amit
next prev parent reply other threads:[~2004-03-15 11:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 21:36 [PATCH][1/3] Update CVS KGDB's serial driver Tom Rini
2004-02-25 21:43 ` [PATCH][2/3] Update CVS KGDB's have kgdb_{schedule,process}_breakpoint Tom Rini
2004-02-25 21:53 ` [PATCH][3/3] Update CVS KGDB's wrt connect / detach Tom Rini
2004-02-26 8:14 ` [Kgdb-bugreport] " Amit S. Kale
2004-02-26 14:41 ` Tom Rini
2004-02-26 16:05 ` Daniel Jacobowitz
2004-02-26 17:44 ` Tom Rini
2004-02-26 23:32 ` Daniel Jacobowitz
2004-03-01 8:12 ` Amit S. Kale
2004-02-26 21:45 ` Pavel Machek
2004-03-01 8:29 ` Amit S. Kale
2004-02-26 18:08 ` Tom Rini
2004-03-01 8:15 ` Amit S. Kale
2004-02-26 23:30 ` George Anzinger
2004-02-26 23:59 ` Tom Rini
2004-02-27 1:57 ` George Anzinger
2004-02-27 15:49 ` Tom Rini
2004-02-27 22:11 ` George Anzinger
2004-02-27 22:50 ` Tom Rini
2004-03-01 10:18 ` Amit S. Kale
2004-03-01 10:17 ` Amit S. Kale
2004-02-27 17:13 ` Tom Rini
2004-02-27 21:55 ` George Anzinger
2004-03-01 8:36 ` Amit S. Kale
2004-03-01 16:31 ` Tom Rini
2004-02-25 22:59 ` [Kgdb-bugreport] [PATCH][2/3] Update CVS KGDB's have kgdb_{schedule,process}_breakpoint George Anzinger
2004-02-25 23:04 ` Tom Rini
2004-02-25 23:23 ` George Anzinger
2004-02-26 7:30 ` Amit S. Kale
2004-02-26 23:19 ` George Anzinger
2004-03-01 8:32 ` Amit S. Kale
2004-03-02 21:19 ` George Anzinger
2004-03-03 5:13 ` Amit S. Kale
2004-03-04 0:20 ` George Anzinger
2004-03-04 4:58 ` Amit S. Kale
2004-03-11 21:28 ` George Anzinger
2004-03-12 4:44 ` Amit S. Kale
2004-03-12 8:03 ` George Anzinger
2004-03-15 11:20 ` Amit S. Kale [this message]
2004-03-15 19:52 ` George Anzinger
2004-03-16 4:30 ` Amit S. Kale
2004-03-16 13:02 ` La Monte H.P. Yarroll
2004-03-16 15:04 ` Amit S. Kale
2004-02-25 23:10 ` [Kgdb-bugreport] [PATCH][1/3] Update CVS KGDB's serial driver George Anzinger
2004-02-25 23:18 ` Tom Rini
2004-02-26 8:25 ` Amit S. Kale
2004-02-26 14:43 ` 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=200403151650.34115.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).