From: Ken Coleman <kencoleman@adsl-66-123-209-51.dsl.snfc21.pacbell.net>
Subject: gdb-ui & Mac OS X...
Date: Sat, 21 Feb 2004 23:41:52 GMT [thread overview]
Message-ID: <m2vfm0yp8o.fsf@adsl-66-123-209-51.dsl.snfc21.pacbell.net> (raw)
Hey everyone,
I've been trying to get gdb-ui working with the CVS version of emacs
under Mac OS X 10.3.2. There are a couple of issues I'm experiencing,
and was wondering if it's a setup problem on my end or a bug in
gdb-ui. Here's what I'm doing.
1. I have a tiny test program in the active buffer, and I do M-x gdba.
2. I run gdba (like this) with the default, which is "gdb -annotate=3
a.out".
3. This gives me multiple errors into the *Messages* buffer. Namely:
error in process filter: gdb-pre-prompt: Phase error in gdb-pre-prompt
(got pre-emacs) error in process filter: Phase error in gdb-pre-prompt
(got pre-emacs)
4. At this point I see the split frame with my test.cxx and the
*gud-a.out* buffer.
5. I choose Gud->GDB-UI->Display other windows and the various other
windows appear in the frame.
6. Now I start debugging the program, but the other windows never
update - the locals, the stack, etc. If I kill them and re-create
them using the various items under the Gud menu, they are
temporarily correct, but they do not update as I am stepping
through the program as I would expect.
7. If I add watches, the speedbar comes up with the watches, but there
are no values for the watched variables, only the watched variable
names.
Is this the expected behavior? Does anyone else have GDB-UI working
well under OS X?
Thanks in advance for any advice!
- Ken.
ken_coleman@iname.com
next reply other threads:[~2004-02-21 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 23:41 Ken Coleman [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 18:53 gdb-ui & Mac OS X Nick Roberts
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=m2vfm0yp8o.fsf@adsl-66-123-209-51.dsl.snfc21.pacbell.net \
--to=kencoleman@adsl-66-123-209-51.dsl.snfc21.pacbell.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.