From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Jerome Guitton <guitton@adacore.com>
Subject: Re: [RFA] arm-pikeos: software single step
Date: Mon, 10 Sep 2018 17:28:00 -0000 [thread overview]
Message-ID: <87sh2hs1n5.fsf@tromey.com> (raw)
In-Reply-To: <1536592407-13448-1-git-send-email-brobecker@adacore.com> (Joel Brobecker's message of "Mon, 10 Sep 2018 17:13:27 +0200")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> The challenge is that, up to now, the PikeOS target was in all respects
Joel> identical to a baremetal target as far as GDB was concerned, meaning
Joel> we were using the baremetal osabi for this target too. This is no longer
Joel> possible, and we need to introduce a new OSABI variant.
I don't really know anything about this area, but...
Is there any chance of introducing some flag into the object files so
that the heuristic could be removed at some future point?
Joel> +
Joel> +static void
Joel> +arm_pikeos_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
The usual thing about functions needing an intro comment.
Joel> + { "Pikeos", NULL },
The email spelled it "PikeOS", so maybe it should read that way here as
well.
Tom
next prev parent reply other threads:[~2018-09-10 17:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 15:13 Joel Brobecker
2018-09-10 17:28 ` Tom Tromey [this message]
2018-09-10 17:43 ` Joel Brobecker
2018-09-10 18:39 ` [RFA v2] " y
2018-09-10 20:01 ` Simon Marchi
2018-09-10 20:53 ` Tom Tromey
2018-09-11 8:56 ` Joel Brobecker
2018-09-11 9:58 ` Simon Marchi
2018-09-11 13:51 ` Joel Brobecker
2018-09-11 15:41 ` Tom Tromey
2018-09-11 21:17 ` Joel Brobecker
2018-09-14 0:47 ` Joel Brobecker
2018-09-14 10:57 ` Simon Marchi
2018-11-01 21:44 ` Joel Brobecker
2018-09-11 9:08 ` [RFA] " Pedro Alves
2018-09-11 11:04 ` Joel Brobecker
2018-09-11 11:27 ` Pedro Alves
2018-09-11 20:57 ` Joel Brobecker
2018-09-12 13:22 ` Pedro Alves
2018-09-14 0:38 ` Joel Brobecker
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=87sh2hs1n5.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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