From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114218 invoked by alias); 12 Nov 2015 20:50:46 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 114206 invoked by uid 89); 12 Nov 2015 20:50:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: ausxippc110.us.dell.com Received: from AUSXIPPC110.us.dell.com (HELO ausxippc110.us.dell.com) (143.166.85.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Thu, 12 Nov 2015 20:50:44 +0000 X-LoopCount0: from 10.170.28.41 From: To: CC: , Subject: Re: (hardware) watchpoints and actions Date: Thu, 12 Nov 2015 20:50:00 -0000 Message-ID: <3D416928-D719-4974-B80E-A994FB15EF1F@dell.com> References: <20151112091432.5c1bb9f86d671edec44bb378f25c04cc.fb8bf6e151.wbe@email03.secureserver.net> <64A9FD4472059B48AC8F38981B7DA5342EF9BD5FDD@MX37A.corp.emc.com> In-Reply-To: <64A9FD4472059B48AC8F38981B7DA5342EF9BD5FDD@MX37A.corp.emc.com> Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00022.txt.bz2 > On Nov 12, 2015, at 3:44 PM, taylor, david wrote: > ... > But the code that supports this type of stuff often works better if it= is compiled into the actual application, which to some degree violates the= "do not ship debug code in production code" rule. >=20 > The code *IS* compiled into the application. The GDB stub is always comp= iled in. >=20 > The stub is NOT debug code. It enables the developer to examine the syst= em, set > breakpoints, tracepoints, watchpoints, or whatever. >=20 > Another rule is to test what you ship. You don't want to debug with the = stub removed.=20 > And if a problem is found in testing, it's much easier to track it down i= f the stub is > compiled in. The stub is always compiled in. It is part of the shipped = product. That's fine if your security mechanisms are good enough to prevent unauthor= ized access to the stub in a production setting. That's the issue that the= "don't ship debug code" rule is concerned with. paul