Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Paul Koning <Paul_Koning@Dell.com>
Cc: Jie Zhang <jie.zhang@analog.com>,
	  Dave Korn <dave.korn.cygwin@googlemail.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Reset breakpoint after load?
Date: Fri, 22 Jan 2010 18:19:00 -0000	[thread overview]
Message-ID: <4B59EBEC.7060800@vmware.com> (raw)
In-Reply-To: <D8CEBB6AE9D43848BD2220619A43F32649F079@M31.equallogic.com>

Paul Koning wrote:
>> On 01/22/2010 10:15 AM, Paul Koning wrote:
>>> Yes, but... doesn't GDB take read-only data from the executable file
>>> rather than from the target?  If so then it should not matter.
>> That's
>>> what "set trust-readonly-sections" does.  Or is it off by default?
>> Turn
>>> it on, that's good for performance anyway.
>>>
>> I just tested this method and confirm that "set
> trust-readonly-sections
>> on" also works. According to the manual, this option is off by
> default.
> 
> Right, I noticed that it's set that way.  I have a GDB with local mods
> for our embedded system work; one of the mods is to change the default
> to "on".  That makes debug much faster and makes sense in any case.
> It's very rare to need it to be off.


We defaulted it to 'off' when first implemented, just to
be conservative.  Haven't heard of it causing any problems
since then, so perhaps it's time to default it to 'on'.


  parent reply	other threads:[~2010-01-22 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  7:36 Jie Zhang
2010-01-21 10:01 ` Dave Korn
2010-01-21 12:52   ` Jie Zhang
2010-01-21 18:29   ` Michael Snyder
2010-01-21 21:20     ` Daniel Jacobowitz
2010-01-21 22:41       ` Jie Zhang
2010-01-22  2:15         ` Paul Koning
2010-01-22  3:05           ` Jie Zhang
2010-01-22 11:46             ` Paul Koning
2010-01-22 13:46               ` Daniel Jacobowitz
2010-01-22 18:19               ` Michael Snyder [this message]
2010-01-21 22:35     ` Jie Zhang

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=4B59EBEC.7060800@vmware.com \
    --to=msnyder@vmware.com \
    --cc=Paul_Koning@Dell.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gdb@sourceware.org \
    --cc=jie.zhang@analog.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