From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1876 invoked by alias); 11 Jun 2010 11:20:09 -0000 Received: (qmail 1861 invoked by uid 48); 11 Jun 2010 11:20:09 -0000 Date: Fri, 11 Jun 2010 11:20:00 -0000 Message-ID: <20100611112009.1860.qmail@sourceware.org> From: "pedro at codesourcery dot com" To: gdb-prs@sourceware.org In-Reply-To: <20100611085114.11692.frederic.riss@gmail.com> References: <20100611085114.11692.frederic.riss@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug threads/11692] GDB internal error when using pthread_attr_setaffinity_np 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: 2010-q2/txt/msg00399.txt.bz2 ------- Additional Comments From pedro at codesourcery dot com 2010-06-11 11:20 ------- Hmmm, problem is linux-thread-db.c is returning a minus_one_ptid to infrun when this happens. See: WL: waitpid Thread 0xb7fe16c0 (LWP 22258) received Stopped (signal) (stopped) LLW: trap ptid is LWP 22262. infrun: target_wait (-1, status) = infrun: -1 [process -1], infrun: status->kind = spurious if (have_threads (ptid)) { /* Change ptids back into the higher level PID + TID format. If the thread is dead and no longer on the thread list, we will get back a dead ptid. This can occur if the thread death event gets postponed by other simultaneous events. In such a case, we want to just ignore the event and continue on. */ ptid = thread_from_lwp (ptid); if (GET_PID (ptid) == -1) ourstatus->kind = TARGET_WAITKIND_SPURIOUS; } inferior -1 will obviously not be in the inferior table. I'm not 100% certain what's best. I've wanted to get rid of TARGET_WAITKIND_SPURIOUS before, this may be the last drop. :-) -- http://sourceware.org/bugzilla/show_bug.cgi?id=11692 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.