From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-6728-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 26038 invoked by alias); 8 Apr 2009 18:49:34 -0000
Received: (qmail 26019 invoked by uid 48); 8 Apr 2009 18:49:33 -0000
Date: Wed, 08 Apr 2009 18:49:00 -0000
From: "GNUtoo at no-log dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Message-ID: <20090408184931.10046.GNUtoo@no-log.org>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug threads/10046] New: internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
X-Bugzilla-Reason: CC
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2009-q2/txt/msg00030.txt.bz2

hi,
I've the following problem when trying to debug wesnoth:
[New LWP 3306]
infrun: TARGET_WAITKIND_STOPPED
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4000e56c
infrun: context switch
infrun: Switching context from LWP 3305 to LWP 3306
infrun: BPSTAT_WHAT_CHECK_SHLIBS
infrun: no stepping, continue
infrun: resume (step=1, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x40011eec
infrun: software single step trap for LWP 3306
infrun: no stepping, continue
infrun: resume (step=0, signal=0)
infrun: prepare_to_wait
[LWP 3306 exited]
[LWP 3305 exited]
infrun: infwait_normal_state
[New LWP 3297]
infrun: TARGET_WAITKIND_STOPPED
/home/embedded/oetmp_openmoko/work/armv4t-angstrom-linux-gnueabi/gdb-6.8-r3/gdb-6.8/gdb/linux-nat.c:1152:
internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

the strange thing is that I didnt play with gdb...I just ran wesnoth with:
gdb wesnoth
run -f -r 480x640
and I've waited until it crashes...I didn't add breakpoints etc...like in this
bugreport:
http://sourceware.org/ml/gdb/2008-08/msg00163.html

-- 
           Summary: internal-error: linux_nat_resume: Assertion `lp != NULL'
                    failed.
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: threads
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: GNUtoo at no-log dot org
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10046

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.