From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: gdba probs
Date: Sat, 7 Dec 2002 02:38:37 +0000 [thread overview]
Message-ID: <15857.24365.637778.876009@nick.uklinux.net> (raw)
In-Reply-To: <200212052149.gB5LnZ504967@rum.cs.yale.edu>
Stefan Monnier writes:
> > Regarding the bunches of errors, they occur because you're using commands
> > that stop/step at the instruction level (break *_start, stepi, etc).
> > Handling these commands is on my TODO list. ;-)
>
> I have no idea what this entails, but maybe it is related to another
> wish of mine: to make it usable when running "gdb --fullname foo".
> Right now, it seems that if gdb is not started with "--annotate=2"
> gdba just "freezes" (typing stuff at gdb prompt leads nowhere).
I don't think they're related. The bunches of errors occur because
gdb-info-breakpoints-custom only parses the output of "info breakpoints"
properly when they are at a statement boundary (have a line no. associated
with them) to place to breakpoint icons. There will be similar problems with
"info frames".
I don't know exactly what happens if gdba starts without "--annotate=2" but
the annotations are needed to tell it the status of the prgram. "--fullname"
just gives line information for display of the source.
Looking at it, gdba doesn't freeze but to seems expect its input to come from
the input/output buffer (try, for example, typing break main in there)
> I understand that with "gdb --fullname foo" most things won't work, but I'd
> like to slowly merge M-x gdb and M-x gdba, so I think that the gdba
> code should be made to work even if the underlying gdb process is not
> configured as expected: it should then behave more or less like M-x gdb does.
You could infer how gdb was running from the lack/type of annotations (=1, =2)
but I don't think this would be easy. At the moment I run two gdb commands
requiring annotations *before* the executable is run to find out in what
file main is stored.
> C-h f replace-regexp ;-)
I've also used insert-buffer. C-h f gives :
This function is meant for the user to run interactively.
Don't call it from programs!
What should I use this time ?
Nick
next prev parent reply other threads:[~2002-12-07 2:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:40 gdba probs Nick Roberts
2002-12-05 21:49 ` Stefan Monnier
2002-12-07 2:38 ` Nick Roberts [this message]
2002-12-07 3:10 ` Miles Bader
2002-12-09 15:46 ` Stefan Monnier
2002-12-10 14:19 ` Stefan Monnier
[not found] ` <15862.30022.647969.267154@nick.uklinux.net>
[not found] ` <200212111411.gBBEBUn03805@rum.cs.yale.edu>
2002-12-11 22:27 ` Nick Roberts
2002-12-11 22:48 ` Stefan Monnier
2002-12-12 0:05 ` Nick Roberts
2002-12-12 13:49 ` Stefan Monnier
2002-12-12 14:13 ` Miles Bader
2002-12-13 22:21 ` Richard Stallman
2002-12-12 1:24 ` Miles Bader
2002-12-12 10:22 ` Kim F. Storm
2002-12-15 0:36 ` Nick Roberts
2002-12-07 21:25 ` Richard Stallman
2002-12-08 1:55 ` Nick Roberts
2002-12-09 20:21 ` Richard Stallman
2002-12-10 21:39 ` Nick Roberts
2002-12-10 23:44 ` Kim F. Storm
2002-12-11 20:40 ` Richard Stallman
2002-12-08 2:27 ` Miles Bader
2002-12-10 14:14 ` Stefan Monnier
2002-12-11 17:45 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 6:19 Miles Bader
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=15857.24365.637778.876009@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).