public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: alex@alex.org.uk To: gdb-gnats@sources.redhat.com Subject: threads/2149: thread_db_get_info: cannot get thread info: generic error on fork()/execvp() Date: Tue, 18 Jul 2006 12:48:00 -0000 [thread overview] Message-ID: <20060718124206.30754.qmail@sourceware.org> (raw) >Number: 2149 >Category: threads >Synopsis: thread_db_get_info: cannot get thread info: generic error on fork()/execvp() >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Tue Jul 18 12:48:01 GMT 2006 >Closed-Date: >Last-Modified: >Originator: alex@alex.org.uk >Release: GNU gdb 6.4-debian >Organization: >Environment: Ubuntu Dapper, stock gdb, stock C compiler, stock libraries Linux polonius 2.6.15-26-amd64-generic #1 SMP PREEMPT Mon Jul 17 19:50:04 UTC 2006 x86_64 GNU/Linux gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) GNU gdb 6.4-debian >Description: On certain calls to fork(), execvp(), gdb does the following: thread_db_get_info: cannot get thread info: generic error after that it is unusable. This is difficult to replicate in the general case, though I have seen it happen several times with the wxWidgets library using the ::wxExecute() function. I have finally got it 100% repeatable (of course, on the function I want to debug...). Sadly it is /not/ repeatable using the minimal wxWidgets sample application for exec. >How-To-Repeat: Download sources to Xara LX (see http://www.xaraxtreme.org/). You will need at least revision r1463. Build a debug version. Run it under gdb. Draw any shape. File->Export. Browse for other folders, select "MIFF File". Chose any file name ending in ".miff" and OK the default options. At imgmgkft.cpp line 1313 it calls ::wxExecute to run "convert" (ImageMagick). This does a fork() and an execvp(). 100% reliably, gdb suffers the above internal error. I don't believe there is anything special about ImageMagick - I've seen similar things happen using the print setup dialog (which runs lp commands), but not reliably. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2006-07-18 12:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-18 12:48 alex [this message] 2006-07-26 21:48 Matthew M. DeLoera 2006-07-31 13:08 Daniel Jacobowitz 2006-08-01 16:38 Matthew M. DeLoera 2006-08-13 20:18 Alex Bligh 2006-08-13 20:38 Alex Bligh 2006-09-10 16:29 drow
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=20060718124206.30754.qmail@sourceware.org \ --to=alex@alex.org.uk \ --cc=gdb-gnats@sources.redhat.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).