From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: esr@snark.thyrsus.com, stephen@xemacs.org, perry@piermont.com,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Defending GCC considered futile
Date: Tue, 10 Feb 2015 21:23:17 +0200 [thread overview]
Message-ID: <83sied7eqi.fsf@gnu.org> (raw)
In-Reply-To: <54DA4BCE.8030804@dancol.org>
> Date: Tue, 10 Feb 2015 10:19:58 -0800
> From: Daniel Colascione <dancol@dancol.org>
> CC: esr@snark.thyrsus.com, stephen@xemacs.org, emacs-devel@gnu.org,
> rms@gnu.org, perry@piermont.com
>
> > I guess we have very different GDB experiences and/or needs, if this
> > is a significant issue for you. I almost never need to type complex
> > source-level expressions into a debugger. The reason is simple:
> > almost every interesting value is already assigned to some variable,
> > so most expressions I type are simple references to variables.
>
> <optimized out>
-Og
> > If you want to explore a complex data structure, you should use Python
> > or Guile scripting anyway.
>
> That scripting is still incomplete. See
> https://sourceware.org/ml/gdb-patches/2014-10/msg00102.html, where I try
> to fix it to some extent. At least IME, sooner or later, when scripting
> GDB, you fall down to issuing textual commands and parsing their textual
> output.
That description doesn't strike me as "the most frustrating part",
rather as a rare and marginal annoyance.
next prev parent reply other threads:[~2015-02-10 19:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 20:29 Defending GCC considered futile Eric S. Raymond
2015-02-07 21:24 ` David Kastrup
2015-02-09 0:04 ` Richard Stallman
2015-02-07 22:30 ` Florian Weimer
2015-02-08 14:12 ` Stefan Monnier
2015-02-09 19:39 ` Florian Weimer
2015-02-09 22:04 ` Perry E. Metzger
2015-02-09 0:04 ` Richard Stallman
2015-02-09 4:13 ` Stefan Monnier
2015-02-09 5:50 ` Stephen J. Turnbull
2015-02-09 22:06 ` Richard Stallman
2015-02-09 22:24 ` Perry E. Metzger
2015-02-10 3:37 ` Eli Zaretskii
2015-02-10 8:30 ` Daniel Colascione
2015-02-10 8:47 ` Helmut Eller
2015-02-10 15:58 ` Eli Zaretskii
2015-02-10 15:57 ` Eli Zaretskii
2015-02-10 18:19 ` Daniel Colascione
2015-02-10 18:41 ` David Kastrup
2015-02-10 19:27 ` Eli Zaretskii
2015-02-10 19:23 ` Eli Zaretskii [this message]
2015-02-10 20:05 ` David Kastrup
2015-02-10 23:14 ` Stefan Monnier
2015-02-11 3:46 ` Eli Zaretskii
2015-02-11 23:11 ` Richard Stallman
2015-02-10 22:48 ` Richard Stallman
2015-02-11 2:08 ` John Yates
2015-02-11 15:42 ` Perry E. Metzger
2015-02-11 16:14 ` Eli Zaretskii
2015-02-11 16:29 ` Perry E. Metzger
2015-02-11 16:44 ` Eli Zaretskii
2015-02-11 16:54 ` Eli Zaretskii
2015-02-11 20:50 ` Perry E. Metzger
2015-02-12 3:37 ` Eli Zaretskii
2015-02-12 3:54 ` Perry E. Metzger
2015-02-11 19:14 ` Florian Weimer
2015-02-11 19:19 ` Stefan Monnier
2015-02-11 23:13 ` Richard Stallman
2015-02-12 1:48 ` raman
2015-02-11 23:13 ` Richard Stallman
2015-02-09 7:41 ` Helmut Eller
2015-02-09 19:30 ` Florian Weimer
2015-02-09 22:41 ` Perry E. Metzger
2015-02-10 22:46 ` Richard Stallman
2015-02-09 22:19 ` Perry E. Metzger
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=83sied7eqi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=perry@piermont.com \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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 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.