From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15073 invoked by alias); 15 Jan 2009 16:00:31 -0000 Received: (qmail 15050 invoked by uid 48); 15 Jan 2009 16:00:29 -0000 Date: Thu, 15 Jan 2009 16:00:00 -0000 From: "muller at ics dot u-strasbg dot fr" To: gdb-prs@sourceware.org Message-ID: <20090115160028.9747.muller@ics.u-strasbg.fr> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug gdb/9747] New: Quit and "(running)" bug X-Bugzilla-Reason: CC 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: 2009-q1/txt/msg00070.txt.bz2 I have troubles with CVS HEAD gdb on cygwin, related to the "(running)" state. But I don't think that this problem is windows specific... Easiest way to reproduce these problems is to: Run gdb with itself: ./gdb ./gdb $ ./gdb ./gdb GNU gdb (GDB) 6.8.50.20090115-cvs Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-cygwin". For bug reporting instructions, please see: ... Setting up the environment for debugging gdb. During symbol reading, struct/union type gets multiply defined: struct type. Breakpoint 1 at 0x40b8a3: file ../../purecvs/gdb/utils.c, line 972. Breakpoint 2 at 0x419086: file ../../purecvs/gdb/cli/cli-cmds.c, line 199. (top-gdb) start Temporary breakpoint 3 at 0x40105c: file ../../purecvs/gdb/gdb.c, line 26. Starting program: /usr/local/src/gdbcvs/build-bare/gdb/gdb.exe [New Thread 3768.0xd98] [New Thread 3768.0xb0] Temporary breakpoint 3, main (argc=1, argv=0xf01f58) at ../../purecvs/gdb/gdb.c:26 26 { (top-gdb) set height 1 (top-gdb) n ---Type to continue, or q to quit---q Quit (top-gdb) set height 80 (top-gdb) inf thr 2 Thread 3768.0xb0 (running) * 1 Thread 3768.0xd98 (running) (top-gdb) cont Continuing. Cannot execute this command while the selected thread is running. (top-gdb) The problem is the set_running function introduced for the non-stop mode probably: the fact on Quitting at the --Type question bypasses the set_running(..,0) (I discovered that by adding an printout on each set_running call) and thus leaves gdb beleaaving that the threads are running while non-stop mode is not even implemented yet on cygwin native gdb! This needs a fix! Pierre Muller Pascal language support maintainer for GDB -- Summary: Quit and "(running)" bug Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned at sourceware dot org ReportedBy: muller at ics dot u-strasbg dot fr CC: gdb-prs at sourceware dot org http://sourceware.org/bugzilla/show_bug.cgi?id=9747 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.