From: "Amit S. Kale" <amitkale@emsyssoft.com>
Organization: EmSysSoft
To: "La Monte H.P. Yarroll" <piggy@timesys.com>
Subject: Re: [Kgdb-bugreport] [PATCH][2/3] Update CVS KGDB's have kgdb_{schedule,process}_breakpoint
Date: Tue, 16 Mar 2004 20:34:24 +0530
User-Agent: KMail/1.5
Cc: George Anzinger <george@mvista.com>, Tom Rini <trini@kernel.crashing.org>,
       kernel list <linux-kernel@vger.kernel.org>,
       Pavel Machek <pavel@suse.cz>, kgdb-bugreport@lists.sourceforge.net
References: <20040225213626.GF1052@smtp.west.cox.net> <200403161000.02223.amitkale@emsyssoft.com> <4056FAF8.9000907@timesys.com>
In-Reply-To: <4056FAF8.9000907@timesys.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200403162034.24341.amitkale@emsyssoft.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2150
Lines: 60

On Tuesday 16 Mar 2004 6:32 pm, La Monte H.P. Yarroll wrote:
> Amit S. Kale wrote:
> >On Tuesday 16 Mar 2004 1:22 am, George Anzinger wrote:
> >>Amit S. Kale wrote:
> >>>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!
> >>
> >>You have a better solution?
> >
> >Nope.
> >
> >I think this feature is very likely to be abused by programmers. They do
> >deserve suffering if they choose to shoot at their own feet.
> >
> >Kernel programmers have to be aware of implementation of this feature if
> > they choose to call arbitrary functions. This includes knowing whether
> > interrupts are disabled, handling of exceptions in gdb called functions,
> > whether other processors run, that breakpoints are  disabled. Given that
> > kgdb is used for learning the kernel, such features are best kept aside.
> >
> >-Amit
>
> Pardon my question.  I've lost track of the thread and the available
> context doesn't really help me.
>
> Is this the ability to step into an arbitrary function from the gdb command
> line or something else?

This is ability to call arbitray function from gdb command line.
Example 
(gdb) p myfunction(1,2,3)
-Amit

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/