public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: Oleg V.Zhylin <vz@yahoo.com> To: gdb-gnats@sources.redhat.com Cc: Jim Blandy <jimb@codesourcery.com> Subject: threads/2292: GDB process stops when debugging threaded program Date: Sat, 28 Jul 2007 00:08:00 -0000 [thread overview] Message-ID: <20070728000737.14583.qmail@sourceware.org> (raw) >Number: 2292 >Category: threads >Synopsis: GDB process stops when debugging threaded program >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Jul 28 00:08:01 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Oleg V. Zhylin <vz@yahoo.com> >Release: GDB CVS 2007-7-27 >Organization: >Environment: Fedora Core 7 >Description: The attached program makes GDB itself stop when run. >How-To-Repeat: Hi Jim, pthread_test.cpp demonstrates the problematic behavior. It is built using g++ -g pthread_test.cpp -lpthread The version numbers are $ cat /proc/version Linux version 2.6.21-1.3228.fc7 (kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue Jun 12 15:37:31 EDT 2007 and gdb snapshot for July 24th $ gdb --version GNU gdb 6.6.50.20070724 Below is the log of gdb session $ gdb a.out GNU gdb 6.6.50.20070724 Copyright (C) 2007 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /home/cartcs/Work/gdb/pthread_create/a.out [Thread debugging using libthread_db enabled] [New Thread 0xb7f336d0 (LWP 22251)] [3]+ Stopped gdb a.out >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="pthread_test.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pthread_test.cpp" I2luY2x1ZGUgPHB0aHJlYWQuaD4NCiNpbmNsdWRlIDxzeXMvdGltZS5oPgoNCnZvaWQgU2xlZXAo dW5zaWduZWQgbG9uZyB1bE1pbGxpc2Vjb25kcykNCnsNCiAgICBzdHJ1Y3QgdGltZXZhbCB0aW1l b3V0Ow0KICAgIHRpbWVvdXQudHZfc2VjID0gMDsNCiAgICB0aW1lb3V0LnR2X3VzZWMgPSB1bE1p bGxpc2Vjb25kcyAqIDEwMDA7DQogICAgc2VsZWN0KDEsIE5VTEwsIE5VTEwsIE5VTEwsICZ0aW1l b3V0KTsNCn0gDQoNCnN0YXRpYyB2b2lkKiB0aHJlYWRGdW5jKCB2b2lkKiBscFBhcmFtICkgDQp7 DQogICBTbGVlcCgzMDAwKTsNCn0NCg0KaW50IG1haW4oKQ0Kew0KICBwdGhyZWFkX2F0dHJfdCBh dHRyOw0KDQogIGludAkJbjsNCiAgYm9vbCByZXMgPSBmYWxzZTsNCg0KICBpZiAoIChuID0gOjpw dGhyZWFkX2F0dHJfaW5pdCgmYXR0cikpICE9IDApDQogIHsNCiAgICByZXR1cm4gLTE7DQogIH0N CiAgcHRocmVhZF90IHRpZDsNCg0KICBpZiAoIChuID0gOjpwdGhyZWFkX2NyZWF0ZSgmdGlkLCAm YXR0ciwgdGhyZWFkRnVuYywgMCkpID09IDApDQogIHsNCg0KICAgIHJlcyA9IHRydWU7DQogIH0N Cg0KICBpZiAoIChuID0gOjpwdGhyZWFkX2F0dHJfZGVzdHJveSgmYXR0cikpICE9IDApDQogIHsN CiAgICByZXR1cm4gLTI7DQogIH0NCiAgaWYgKCFyZXMpDQogIHsNCiAgICByZXR1cm4gLTM7DQog IH0NCiAgU2xlZXAoNTAwMCk7DQoNCiAgcmV0dXJuIDA7DQp9Cg==
next reply other threads:[~2007-07-28 0:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-28 0:08 Oleg V.Zhylin [this message] 2007-07-28 0:18 Jim Blandy 2007-07-28 0:19 jimb 2007-11-13 1:48 Oleg V. Zhylin
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=20070728000737.14583.qmail@sourceware.org \ --to=vz@yahoo.com \ --cc=gdb-gnats@sources.redhat.com \ --cc=jimb@codesourcery.com \ /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).