From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>
Subject: Re: corelow and threads question
Date: Sat, 06 Jun 2009 00:01:00 -0000 [thread overview]
Message-ID: <200906060101.46372.pedro@codesourcery.com> (raw)
In-Reply-To: <h0bsb7$vo3$1@ger.gmane.org>
On Friday 05 June 2009 20:40:23, Aleksandar Ristovski wrote:
> I am inclined to think that core_ops is the right way to go;
> at which point should I do a "push_target" in that case?
It is not the "right" way to go. It will work for a native
nto gdb, but it is not acceptable for mainline. The core debugging
support should work on cross configurations too. If you have
anything core support related that depends on the host where gdb was
configured, you have a design bug. With such a hack, a
multi-arch nto gdb breaks when debugging cores from other
architectures (your core_ops overrides will kick in, although
the core being debugged isn't nto). A multi-arch gdb
(e.g., --enable-targets=all) on e.g., a linux host, wouldn't
be able to cross debug nto cores the same as a native
nto gdb, as it would miss the overrides.
--
Pedro Alves
next prev parent reply other threads:[~2009-06-06 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 18:55 Aleksandar Ristovski
2009-06-05 19:03 ` Daniel Jacobowitz
2009-06-05 19:20 ` Aleksandar Ristovski
2009-06-05 19:24 ` Pedro Alves
2009-06-05 19:41 ` Aleksandar Ristovski
2009-06-06 0:01 ` Pedro Alves [this message]
2009-06-06 0:27 ` Pedro Alves
2009-06-09 16:10 ` Aleksandar Ristovski
2009-06-10 16:49 ` Pedro Alves
2009-06-10 20:38 ` Aleksandar Ristovski
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=200906060101.46372.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=aristovski@qnx.com \
--cc=gdb@sourceware.org \
/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