From: Nick Roberts <nickrob@gnu.org>
Cc: schwab@suse.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: gdb-ui can't handle mutiple debugging sessions
Date: Wed, 15 Sep 2004 15:39:17 +1200 [thread overview]
Message-ID: <000401c49ad5$e94a78e0$bc9260cb@h> (raw)
In-Reply-To: 200409140219.LAA13033@etlken.m17n.org
> I'm writing a C library. I also wrote several programs that
> use that library to test it. So, it's important for me to
> use a single Emacs session to run those test programs under
> multiple gdb sessions...
Why can't you test the library with your programs in a serial fashion?
Do you really need to start the second test before finishing the first?
(I'm sure you do, but I'm just trying to understand how and when the
need arises)
> ...In that situation, when I want to
> set a breakpoint in some file of the library by C-x SPC, its
> usually for a gdb buffer that I visited most recently.
> Otherwise, I'd like to type C-u C-x SPC and expect Emacs to
> ask me for which gdb buffer to set the break point.
Perhaps we could implement that behaviour for 'gdb -fullname'
(assuming it doesn't already have it).
Nick
next prev parent reply other threads:[~2004-09-15 3:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 20:06 gdb-ui can't handle mutiple debugging sessions Andreas Schwab
2004-09-12 22:12 ` Nick Roberts
2004-09-12 22:49 ` Stefan
2004-09-12 23:32 ` Andreas Schwab
2004-09-12 23:44 ` Miles Bader
2004-09-13 3:17 ` Stefan
2004-09-14 1:33 ` Nick Roberts
2004-09-14 2:19 ` Kenichi Handa
2004-09-15 3:39 ` Nick Roberts [this message]
2004-09-15 4:10 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 13:22 Zoltan Kemenczy
2004-09-15 21:08 Nick Roberts
2004-09-15 22:05 Zoltan Kemenczy
2004-09-15 22:16 ` Stefan Monnier
2004-09-16 0:05 Zoltan Kemenczy
2004-09-16 13:58 ` Stefan
2004-09-17 4:17 ` 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='000401c49ad5$e94a78e0$bc9260cb@h' \
--to=nickrob@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.de \
/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.