From: Tristan Gingold <gingold@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>,
Rupp Douglas <rupp@adacore.com>
Subject: Re: RFA: New port: ia64-hp-openvms - the stub
Date: Fri, 24 Feb 2012 09:24:00 -0000 [thread overview]
Message-ID: <6B97507D-F782-4A58-A10E-AD6A32CE49D6@adacore.com> (raw)
In-Reply-To: <4F45478D.2030802@redhat.com>
On Feb 22, 2012, at 8:52 PM, Pedro Alves wrote:
> On 02/21/2012 04:30 PM, Tristan Gingold wrote:
>>
>> On Feb 14, 2012, at 7:08 PM, Pedro Alves wrote:
>
>>> I couldn't really tell, but you may want to consider looking into xml target
>>> descriptions. At least reporting a description with the openvms osabi would
>>> be good.
>>
>> I plan to fix the register issue soon, just be patient !
>
> I am. :-) A description with at least the osabi is good so that gdb
> knows the target's osabi even if the user doesn't supply an executable.
Ok, shouldn't be hard to do. Just to implement qXfer:features:read, IIUC.
>>>> +#if 1
>>>> + /* What a mess. Gdb and linux expects bsp to point after the current
>>>> + register frame. Adjust. */
>>>
>>> What does this mean? Are we committing to a hack that will make our
>>> lives hard when we want to fix it?
>>
>> I have updated the comment. Currently, ia64-tdep.c follows the Linux convention, and we don't want to change that. So the BSP has to be adjusted.
>
> Why don't we want to change it?
I think it's too late. That would be a change in gdbserver and other stubs, so it would break compatibility. The adjustment in the VMS stubs isn't that complex.
> It'd be good if the basics of using the stub were documented in
> the manual.
Sure, I will work on that.
> In any case, this is okay.
Thank you for reviewing,
Tristan.
next prev parent reply other threads:[~2012-02-24 8:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 13:07 RFA: New port: ia64-hp-openvms (0/3) Tristan Gingold
2012-02-10 13:21 ` RFA: New port: ia64-hp-openvms (1/3) - new osabi Tristan Gingold
2012-02-10 13:27 ` RFA: New port: ia64-hp-openvms (3/3) - ia64-vms-tdep.c Tristan Gingold
2012-02-14 17:50 ` Pedro Alves
2012-02-15 9:14 ` Tristan Gingold
2012-02-15 12:57 ` Pedro Alves
2012-02-21 16:23 ` Tristan Gingold
2012-02-22 19:39 ` Pedro Alves
2012-02-22 19:53 ` Douglas Rupp
2012-02-24 14:17 ` Tristan Gingold
2012-02-24 14:16 ` Tristan Gingold
2012-02-24 14:29 ` Pedro Alves
2012-03-05 11:58 ` Tristan Gingold
2012-02-12 9:36 ` RFA: New port: ia64-hp-openvms (1/3) - new osabi Mark Kettenis
2012-02-10 13:23 ` RFA: New port: ia64-hp-openvms (2/3) Tristan Gingold
2012-02-12 9:39 ` Mark Kettenis
2012-02-13 8:45 ` Tristan Gingold
2012-02-14 17:36 ` Pedro Alves
2012-02-14 17:40 ` Pedro Alves
2012-02-21 16:08 ` RFA: New port: ia64-hp-openvms (2/3) - v2 Tristan Gingold
2012-02-22 19:41 ` Pedro Alves
2012-02-10 13:44 ` RFA: New port: ia64-hp-openvms - the stub Tristan Gingold
2012-02-10 19:06 ` Douglas Rupp
2012-02-13 8:43 ` Tristan Gingold
2012-02-14 18:09 ` Pedro Alves
2012-02-21 17:08 ` Tristan Gingold
2012-02-22 20:25 ` Pedro Alves
2012-02-24 9:24 ` Tristan Gingold [this message]
2012-02-24 11:06 ` Pedro Alves
2012-02-24 11:24 ` Tristan Gingold
2012-02-24 12:17 ` Pedro Alves
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=6B97507D-F782-4A58-A10E-AD6A32CE49D6@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=rupp@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