From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23659 invoked by alias); 8 Sep 2013 15:13:37 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 23650 invoked by uid 89); 8 Sep 2013 15:13:37 -0000 Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 08 Sep 2013 15:13:37 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.2 X-HELO: mtaout20.012.net.il Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MST00E00BI79G00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Sun, 08 Sep 2013 18:13:15 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MST00DR8BM3QL70@a-mtaout20.012.net.il>; Sun, 08 Sep 2013 18:13:15 +0300 (IDT) Date: Sun, 08 Sep 2013 15:13:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 4/7] Trust readonly sections if target has memory protection In-reply-to: <1378641807-24256-5-git-send-email-yao@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <831u4zl52v.fsf@gnu.org> References: <1378432920-7731-1-git-send-email-yao@codesourcery.com> <1378641807-24256-1-git-send-email-yao@codesourcery.com> <1378641807-24256-5-git-send-email-yao@codesourcery.com> X-IsSubscribed: yes X-SW-Source: 2013-09/txt/msg00268.txt.bz2 > From: Yao Qi > Date: Sun, 8 Sep 2013 20:03:24 +0800 > > int > +default_has_memory_protection (struct gdbarch *gdbarch) > +{ > + /* Simply say no. */ > + return 0; > +} Do most of our supported targets have or don't have memory protection? How about most native targets? If a large subset of targets have the protection, it might make more sense to say YES by default, not NO.