public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "muller at ics dot u-strasbg dot fr" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/9747] New: Quit and "(running)" bug Date: Thu, 15 Jan 2009 16:00:00 -0000 [thread overview] Message-ID: <20090115160028.9747.muller@ics.u-strasbg.fr> (raw) 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 <http://gnu.org/licenses/gpl.html> 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: <http://www.gnu.org/software/gdb/bugs/>... 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 <return> to continue, or q <return> 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 <return> 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.
next reply other threads:[~2009-01-15 16:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-15 16:00 muller at ics dot u-strasbg dot fr [this message] 2009-01-15 16:05 ` [Bug gdb/9747] " pedro at codesourcery dot com 2009-01-18 17:42 ` cvs-commit at gcc dot gnu dot org 2009-01-18 17:58 ` pedro at codesourcery dot com 2009-01-20 12:34 ` luisgpm at linux dot vnet dot ibm dot com 2009-01-20 12:57 ` pedro at codesourcery dot com 2009-01-20 19:26 ` luisgpm at linux dot vnet dot ibm dot com 2009-01-22 15:54 ` pedro at codesourcery dot com 2009-01-22 15:56 ` pedro at codesourcery dot com 2009-01-26 13:05 ` luisgpm at linux dot vnet dot ibm dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20090115160028.9747.muller@ics.u-strasbg.fr \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).