From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-23993-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27221 invoked by alias); 20 Jan 2006 04:42:52 -0000
Received: (qmail 27213 invoked by uid 22791); 20 Jan 2006 04:42:52 -0000
X-Spam-Check-By: sourceware.org
Received: from uproxy.gmail.com (HELO uproxy.gmail.com) (66.249.92.195)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Jan 2006 04:42:49 +0000
Received: by uproxy.gmail.com with SMTP id u2so164800uge         for <gdb@sourceware.org>; Thu, 19 Jan 2006 20:42:46 -0800 (PST)
Received: by 10.48.232.18 with SMTP id e18mr110061nfh;         Thu, 19 Jan 2006 20:42:46 -0800 (PST)
Received: by 10.48.236.5 with HTTP; Thu, 19 Jan 2006 20:42:46 -0800 (PST)
Message-ID: <6f48278f0601192042n10a133a1q92101c8a519b4454@mail.gmail.com>
Date: Fri, 20 Jan 2006 20:29:00 -0000
From: Jie Zhang <jzhang918@gmail.com>
To: John Williams <jwilliams@itee.uq.edu.au>
Subject: Re: Triggering qSymbol packets
Cc: gdb@sourceware.org
In-Reply-To: <43CED634.4050503@itee.uq.edu.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43CED634.4050503@itee.uq.edu.au>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-01/txt/msg00193.txt.bz2

On 1/19/06, John Williams <jwilliams@itee.uq.edu.au> wrote:
>
> This is a pretty specific issue - not sure if gdbserver+threads+noMMU
> Linux has ever been done before.  So, I suppose my question(s) are:
>
Yes. Debugging multithreading application using GDB/gdbserver works
pretty well on uClinux for Blackfin. You can find our test result in
file "toolchain_test_results_2005R4.tar.gz" on this page:
<http://blackfin.uclinux.org/frs/?group_id=3D18>.

> 1. has this been reported as an issue before, maybe resolved in a newer
> gdb? (I've googled for 2 days and found no direct answer, just many
> different pieces of the puzzle)
>
It's better to upgrade to the newest version. Our test is done on GDB
6.3 with some backports from 6.4.

> 2. Am I correct thinking that for gdbserver+threads the user must
> manually do the gdb "sym" command to trigger the qSymbol packet, and
> thus initialise linuxthreads_db?
>
I think "file" followed by "target remote" should work.

Jie