From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3270 invoked by alias); 13 Jul 2016 20:39:03 -0000 Mailing-List: contact gdb-testers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-testers-owner@sourceware.org Received: (qmail 3246 invoked by uid 89); 13 Jul 2016 20:39:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=decent X-HELO: kwanyin.sergiodj.net Received: from kwanyin.sergiodj.net (HELO kwanyin.sergiodj.net) (176.31.208.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 13 Jul 2016 20:38:52 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [binutils-gdb] use user_breakpoint_p in python code From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Message-Id: <43684a7b844bce64735940b55b667f7086fa3d44@gdb-build> Date: Wed, 13 Jul 2016 20:39:00 -0000 X-SW-Source: 2016-q3/txt/msg00538.txt.bz2 *** TEST RESULTS FOR COMMIT 43684a7b844bce64735940b55b667f7086fa3d44 *** Author: Tom Tromey Branch: master Commit: 43684a7b844bce64735940b55b667f7086fa3d44 use user_breakpoint_p in python code I noticed that bppy_get_visibility and gdbpy_breakpoint_created implemented their own visibility checks, but subtly different from user_breakpoint_p. I think the latter is more correct, and so changed the Python code to use it. I suspect there isn't a decent way to test this, so no new test. Built and regtested on x86-64 Fedora 23. 2016-07-13 Tom Tromey * python/py-breakpoint.c (bppy_get_visibility) (gdbpy_breakpoint_created): Use user_breakpoint_p.