From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 652 invoked by alias); 24 Mar 2015 15:09:58 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 630 invoked by uid 48); 24 Mar 2015 15:09:58 -0000 From: "antoine.tremblay at ericsson dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/16551] Execution stops when encountering a dprintf with an invalid string Date: Tue, 24 Mar 2015 17:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 7.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: antoine.tremblay at ericsson dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: antoine.tremblay at ericsson dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q1/txt/msg00481.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16551 --- Comment #3 from Antoine Tremblay --- After much thought and some discussion on the gdb ml... There was a few options : Having a generic *stopped,error="xxx" event : was ruled out due to the complexity of making this generic in gdb... unfortuanately we can't update the thread state properly in case of error because of implementation details see : https://sourceware.org/ml/gdb-patches/2015-02/msg00701.html Having an *error aync message : This seemed like a good idea but it would impact all the calls to print_exception, to be mi aware and sync/async aware too, it seems like a bad idea code wise to mix that code. We're left with the option to treat messages that start with "&" as a signal to let the frontend know it should refresh it state. I think this is the best option now since it basically does what the *error async message would do and it's already implemented cleanly in gdb. Note that the "&" prefix is directly associated with a print to stderr in gdb, so we can safely assume it's an error signal. So opon receiving a message starting with & the front end would refresh it's state.. Marc does that sounds like an option for eclipse ? -- You are receiving this mail because: You are on the CC list for the bug.