From: Jie Zhang <jzhang918@gmail.com>
To: John Williams <jwilliams@itee.uq.edu.au>
Cc: gdb@sourceware.org
Subject: Re: Triggering qSymbol packets
Date: Fri, 20 Jan 2006 20:29:00 -0000 [thread overview]
Message-ID: <6f48278f0601192042n10a133a1q92101c8a519b4454@mail.gmail.com> (raw)
In-Reply-To: <43CED634.4050503@itee.uq.edu.au>
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=18>.
> 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
prev parent reply other threads:[~2006-01-20 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:19 John Williams
2006-01-19 0:46 ` Daniel Jacobowitz
2006-01-19 0:50 ` John Williams
2006-01-19 1:18 ` Jim Blandy
2006-01-19 3:26 ` Daniel Jacobowitz
2006-01-20 4:42 ` John Williams
2006-01-20 20:29 ` Jie Zhang [this message]
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=6f48278f0601192042n10a133a1q92101c8a519b4454@mail.gmail.com \
--to=jzhang918@gmail.com \
--cc=gdb@sourceware.org \
--cc=jwilliams@itee.uq.edu.au \
/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: link
Be 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