From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26415 invoked by alias); 9 May 2012 08:04:17 -0000 Received: (qmail 26388 invoked by uid 22791); 9 May 2012 08:04:15 -0000 X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 May 2012 08:04:04 +0000 From: "qiyao at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/13860] Fail in gdb.mi/mi-solib.exp in async mode Date: Wed, 09 May 2012 08:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: qiyao at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: qiyao at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-q2/txt/msg00099.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13860 --- Comment #8 from Yao Qi 2012-05-09 08:03:52 UTC --- (In reply to comment #7) > (In reply to comment #6) > > I think there's more to it than this. > > > > - -exec-run vs "run" gives different MI output. > > > > Oh, I didn't notice this. > > > - The ~"Stopped due to shared library event (no libraries added or removed)\n" > > bit is not output in async, when the user issues a CLI command. Or more > > Yes, I find this line doesn't exits in async gdb.log. > > > generally, CLI execution commands don't produce output when the command > > finishes in async mode (e.g., "next"). I think they should, for the benefit of > > the user doing commands in the gdb console of a frontend (such as Eclipse). > > That sounds like a serious problem, IMO. I agree with you that command output > should be produced, no matter which mode (sync vs. async) gdb is running on. > > Existing mi test cases don't check much about CLI output, which should be > improved. My patch posted in comment#5 fixes this fail, but causes some regressions in both sync mode and async mode, -PASS: gdb.mi/mi2-simplerun.exp: exec-finish +FAIL: gdb.mi/mi2-simplerun.exp: exec-finish (unknown output after running) -PASS: gdb.mi/mi-simplerun.exp: exec-finish +FAIL: gdb.mi/mi-simplerun.exp: exec-finish (unknown output after running) They are about the two points you mentioned in comment#6. You looked far ahead a little bit :) -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.