From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: Re: gdb/725: Crash using debug target and regcaches (in 5.3 branch?)]
Date: Tue, 26 Nov 2002 06:48:00 -0000 [thread overview]
Message-ID: <3DE389B3.9060904@redhat.com> (raw)
In-Reply-To: <3DDD6150.10407@redhat.com>
> FYI,
>
> Too many memory reads/writes was one reason for a ptrace'd threaded shlib program running slow, I suspect this is the other.
To correct this.
This should be a reason why GDB runs slow on GNU/Linux, but, isn't! Per
other thread, this inefficiency (a few 1 000 stray ptrace calls() is
trivialized by the millions (yes >1 000 000) memory read ptrace calls.
GDB was probably executing more memory ptrace() calls than the target
program executes instructions .... (yea, right :-).
Andrew
prev parent reply other threads:[~2002-11-26 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 14:42 Andrew Cagney
2002-11-21 16:14 ` Daniel Jacobowitz
2002-11-21 16:43 ` Andrew Cagney
2002-11-21 17:38 ` Andrew Cagney
2002-11-21 18:37 ` Daniel Jacobowitz
2002-11-25 17:41 ` Daniel Jacobowitz
2002-11-25 18:00 ` Michael Snyder
2002-11-26 6:48 ` Andrew Cagney [this message]
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=3DE389B3.9060904@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
/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