From: Nick Roberts <nickrob@snap.net.nz>
To: "Sanjeev Kumar.S" <sanjeevfiles@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: kgdb in emacs
Date: Sun, 27 Jan 2008 22:23:51 +1300 [thread overview]
Message-ID: <18332.19879.672102.308829@kahikatea.snap.net.nz> (raw)
In-Reply-To: <177972.91003.qm@web57709.mail.re3.yahoo.com>
> Thank you very much Nick, Your clue of emacs version prompted me
> to upgrade my emacs. after which I'm able to do it.
I guess you mean Emacs now parses your command line now.
But presumably you still get *gud-cuad0* in the mode-line of the GUD
buffer.
> BTW, my earlier emacs version was 21.2.4 and now it is 22.0.50.1
>
> One more question: I'm still not able to open the file another emacs
> window. I thought this was supposed happen automatically. In other
> instances of emacs ( like when debugging apps ) the source code file
> opens automatically in another emacs window ( vertical split style).
I have some more thoughts but you need to answer my questions for good
communication.
Does kgdb work like gdb?
Is "target remote /dev/cuad0" a valid kgdb command?
> Even if it doesn't, when I enter "f" it opens up automatically.
For the source to appear gdb/kgdb must output annotations. In gdb, this
requires "--fullname" or "-annotate=1" for text mode and "-annotate=3"
for graphical mode. In Emacs 21 "--fullname" was used but was not visible
to the user.
In Emacs 22, running an app like this:
Run gdb (like this): gdb myprog
won't display the source, but:
Run gdb (like this): gdb -annotate=3 myprog
will. Likewise, I suspect
Run gdb ( like this ) : kgdb -r /dev/cuad0 kernel.debug
won't display the source, but:
Run gdb ( like this ) : kgdb -a -a -a -r /dev/cuad0 kernel.debug
will.
> One possibility is, though i changed the emacs current directory
> to /usr/obj/usr/src/sys/MYKERNEL/ , the -r /dev/cuad0 option would have
> changed the default directory, as evident in the file line when a gud
> window is opened:
> Current directory is /dev/
> :(
You really want to find another way of specifying the arguments along the lines
that I suggested, so that the directory doesn't change and you get
*gud-kernel.debug* in the mode-line of the GUD buffer. However, I think
another way to stop the current directory from changing is to set
gud-chdir-before-run to nil.
One last thing, if you do get it to work well, please e-mail me what you
have learnt so that I can add it to my homepage.
Thanks,
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-27 9:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:14 Mysterious hidden end of line characters David
2008-01-26 19:21 ` Thierry Volpiatto
2008-01-26 19:54 ` David
2008-01-26 20:06 ` David
2008-01-26 20:08 ` David
[not found] ` <mailman.6584.1201377847.18990.help-gnu-emacs@gnu.org>
2008-01-27 6:10 ` Tim X
2008-01-27 7:17 ` kgdb in emacs Sanjeev Kumar.S
2008-01-27 8:26 ` Nick Roberts
2008-01-27 8:53 ` Sanjeev Kumar.S
2008-01-27 9:23 ` Nick Roberts [this message]
2008-01-27 10:17 ` Sanjeev Kumar.S
2008-01-27 10:51 ` Nick Roberts
2008-01-27 11:21 ` Sanjeev Kumar.S
2008-01-27 20:40 ` Nick Roberts
2008-01-26 20:41 ` Mysterious hidden end of line characters Peter Dyballa
2008-01-30 15:04 ` David
[not found] ` <mailman.6748.1201705322.18990.help-gnu-emacs@gnu.org>
2008-01-31 6:21 ` Tim X
2008-01-31 10:20 ` Thierry Volpiatto
2008-01-31 11:17 ` Peter Dyballa
2008-01-31 12:44 ` Thierry Volpiatto
2008-01-31 16:04 ` Thierry Volpiatto
2008-01-31 16:12 ` Thierry Volpiatto
2008-01-31 16:40 ` Thierry Volpiatto
2008-02-02 14:18 ` Thierry Volpiatto
2008-02-04 13:00 ` Thierry Volpiatto
2008-02-04 13:10 ` Thierry Volpiatto
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18332.19879.672102.308829@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=help-gnu-emacs@gnu.org \
--cc=sanjeevfiles@yahoo.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).