From: Todd.Kneisel@Bull.com
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb6.0 and statically linked threaded programs
Date: Sat, 25 Oct 2003 00:09:00 -0000 [thread overview]
Message-ID: <OFE6C04D5F.DD2C590A-ON07256DC9.0083182F-07256DCA.0000EA18@az05.bull.com> (raw)
> On Thu, Oct 23, 2003 at 01:33:55PM -0700, Todd.Kneisel@Bull.com wrote:
> > I just tried gdbserver and it's broken worse than native gdb. For both
> > statically and dynamically linked threaded programs, gdbserver fails
> > the same way that native gdb does for statically linked programs.
>
> Then you have gdbserver set up wrong or are using an older version -
> I've tested it recently. You'll have to investigate more.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
I've found that gdbserver is failing because we're on an ia64 system.
The configure.srv file uses the default srv_linux_thread_db=no for ia64
systems, which disables the code that initializes the thread layer.
I changed srv_linux_thread_db to yes and reconfigured and now the thread
layer is initialized, but breakpoints are not implemented for the ia64
in gdbserver.
We're evaluating our options now. We may go back to gdb 5 and live without
the stack traces that were fixed for ia64 in gdb 6.
Thanks for your help,
Todd Kneisel.
next reply other threads:[~2003-10-25 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 0:09 Todd.Kneisel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 20:34 Todd.Kneisel
2003-10-23 20:35 ` Daniel Jacobowitz
2003-10-24 21:01 ` Andrew Cagney
2003-10-22 23:00 Todd.Kneisel
2003-10-23 12:24 ` Daniel Jacobowitz
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=OFE6C04D5F.DD2C590A-ON07256DC9.0083182F-07256DCA.0000EA18@az05.bull.com \
--to=todd.kneisel@bull.com \
--cc=drow@mvista.com \
--cc=gdb@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: 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