public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Pavel Machek <pavel@suse.cz>,
	"Amit S. Kale" <amitkale@emsyssoft.com>,
	Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: Re: kgdb: rename i386-stub.c to kgdb.c
Date: Thu, 26 Feb 2004 15:07:44 -0800	[thread overview]
Message-ID: <403E7C40.9060603@mvista.com> (raw)
In-Reply-To: <20040226042454.GA31771@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Wed, Feb 25, 2004 at 02:31:12PM -0800, George Anzinger wrote:
> 
>>I would guess it is a problem in the emacs interface where one points at a 
>>location in the code window and enters a command to set a break point ( I 
>>think it is "^x " (control X space)).  It would appear that emacs then only 
>>sends the file name to gdb rather than the full path.
>>
>>This is not a show stopping problem, only confusing.  Once gdb figures out 
>>the right source, all is well.  I usually do it by setting a break point at 
>>the function by name, thus avoiding the point and grunt thing.
> 
> 
> This is a known problem in the emacs interfaces; it will be fixed, but
> I have no idea when the fixed version will be available :)
> 
I agree AND I have bigger fish to fry with emacs so....
-- 
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


      reply	other threads:[~2004-02-26 23:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 13:06 kgdb: rename i386-stub.c to kgdb.c Pavel Machek
2004-02-25  7:33 ` Amit S. Kale
2004-02-25 10:37   ` Pavel Machek
2004-02-25 10:59     ` Amit S. Kale
2004-02-25 11:10       ` Pavel Machek
2004-02-25 11:23         ` Amit S. Kale
2004-02-25 21:17     ` [Kgdb-bugreport] " George Anzinger
2004-02-25 21:25       ` Pavel Machek
2004-02-25 21:28       ` Tom Rini
2004-02-25 22:31         ` George Anzinger
2004-02-26  4:24           ` Daniel Jacobowitz
2004-02-26 23:07             ` George Anzinger [this message]

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=403E7C40.9060603@mvista.com \
    --to=george@mvista.com \
    --cc=amitkale@emsyssoft.com \
    --cc=dan@debian.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox