From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: emacs doesn't use the X clipboard
Date: Sat, 17 Jan 2004 20:41:23 +0200 [thread overview]
Message-ID: <6480-Sat17Jan2004204123+0200-eliz@elta.co.il> (raw)
In-Reply-To: <m3hdyygqfi.fsf@mika.informatik.uni-freiburg.de> (message from LEE Sau Dan on 14 Jan 2004 22:40:01 +0100)
> From: LEE Sau Dan <danlee@informatik.uni-freiburg.de>
> Newsgroups: gnu.emacs.help
> Date: 14 Jan 2004 22:40:01 +0100
>
> >>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
>
> >> I'm not sure if ltrace can show the Xlib calls, though.
>
> Eli> I doubt that. And debugging with ltrace or similar tools is
> Eli> not a very efficient method, anyway, compared to stepping
> Eli> with GDB thru the source code. IMHO, ltrace is for the
> Eli> software to which you don't have the sources.
>
> I don't agree.
I guess we have different experience to draw upon, then.
My experience tells me that trace interpretation is a painstakingly
slow process, compared to stepping with a debugger. It also requires
lots of knowledge of system internals, which many programmers lack.
By contrast, getting the sources and rebuilding with debug info is
nowadays a matter of several dozen minutes.
next prev parent reply other threads:[~2004-01-17 18:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 0:26 emacs doesn't use the X clipboard Micha Feigin
2004-01-11 5:46 ` Eli Zaretskii
[not found] ` <mailman.387.1073803639.928.help-gnu-emacs@gnu.org>
2004-01-12 17:59 ` LEE Sau Dan
2004-01-13 0:18 ` Carsten Weinberg
[not found] ` <mailman.495.1073964322.928.help-gnu-emacs@gnu.org>
2004-01-13 5:00 ` Ian Zimmerman
2004-01-13 12:06 ` LEE Sau Dan
2004-01-13 18:35 ` Carsten Weinberg
2004-01-14 6:37 ` Eli Zaretskii
2004-01-14 7:59 ` Micha Feigin
2004-01-14 13:33 ` Eli Zaretskii
2004-01-14 7:16 ` Micha Feigin
[not found] ` <mailman.606.1074062176.928.help-gnu-emacs@gnu.org>
2004-01-14 21:40 ` LEE Sau Dan
2004-01-17 18:41 ` Eli Zaretskii [this message]
[not found] ` <mailman.665.1074118187.928.help-gnu-emacs@gnu.org>
2004-01-15 12:49 ` Kester Clegg
2004-01-22 21:29 ` Jeff
2004-01-13 11:23 ` Jens Schmidt
2004-01-13 12:22 ` LEE Sau Dan
2004-01-15 12:51 ` Kester Clegg
2004-01-15 21:44 ` LEE Sau Dan
2004-01-18 23:54 ` Ian Zimmerman
2004-01-15 16:26 ` Jens Schmidt
2004-01-13 14:38 ` Tim McNamara
2004-01-13 22:19 ` LEE Sau Dan
2004-01-13 6:48 ` Eli Zaretskii
[not found] ` <mailman.510.1073976607.928.help-gnu-emacs@gnu.org>
2004-01-13 12:28 ` LEE Sau Dan
2004-01-13 15:50 ` Maurizio Loreti
2004-01-13 18:13 ` Gian Uberto Lauri
2004-01-13 22:14 ` LEE Sau Dan
[not found] ` <mailman.545.1074017499.928.help-gnu-emacs@gnu.org>
2004-01-15 12:54 ` Kester Clegg
2004-01-15 21:56 ` LEE Sau Dan
2004-01-13 17:19 ` Eli Zaretskii
[not found] ` <mailman.542.1074014317.928.help-gnu-emacs@gnu.org>
2004-01-14 21:34 ` LEE Sau Dan
[not found] <mailman.381.1073784888.928.help-gnu-emacs@gnu.org>
2004-01-11 13:02 ` Henrik Enberg
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=6480-Sat17Jan2004204123+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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).