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 (3/3) - ia64-vms-tdep.c
Date: Wed, 15 Feb 2012 09:14:00 -0000 [thread overview]
Message-ID: <3F9413FC-FB03-4970-B9FB-C628E5663826@adacore.com> (raw)
In-Reply-To: <4F3A9ED3.7090408@redhat.com>
On Feb 14, 2012, at 6:50 PM, Pedro Alves wrote:
First, thank you for your review. I am currently addressing your points.
[…]
>
>> + info_len = extract_unsigned_integer (buf + 0, 4, byte_order);
>> + pi->unwind_info_size = 8 * info_len;
>> +
>> + /* Read info. */
>> + pi->unwind_info = malloc (pi->unwind_info_size);
>
> xmalloc
Humm, do we want to exit abruptly in case of memory error ? Note that we test the return status.
(OTOH, if malloc fails here, it is likely that the next xmalloc will too).
>
>> + if (!pi->unwind_info)
>> + return -UNW_ENOMEM;
>> +
>> + res = target_read_memory (table_addr + 8,
>> + pi->unwind_info, pi->unwind_info_size);
>> + if (res != 0)
>> + {
>> + free (pi->unwind_info);
>
> xfree
>
>> + pi->unwind_info = NULL;
>> + return -UNW_ENOINFO;
>> + }
>> +
>> + /* FIXME: OSSD. */
>
> What's this? What's OSSD? What's left to fix? Can we fix it?
OS Specific Data. That's an extension of unwinding info on VMS, that is not handled by libunwind.
OTOH, I haven't seen them currently. I suppose they are used only in very specific context (kernel ?)
>> +
>> + pi->lsda = table_addr + 8 + pi->unwind_info_size;
>> + if (extract_unsigned_integer (buf + 4, 2, byte_order) & 3)
>> + {
>> + pi->lsda += 8;
>> + pi->handler = 0; /* FIXME: wrong, but who cares. */
>
> I don't know. But I think this needs a better comment.
Sure.
[…]
>
> Otherwise looks fine. I can't really comment on the vms or ia64 specifics.
>
> Just please make sure an --enable-targets=all build doesn't break
> unexpectedly.
Will do.
Thanks,
Tristan.
next prev parent reply other threads:[~2012-02-15 8:05 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 [this message]
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
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=3F9413FC-FB03-4970-B9FB-C628E5663826@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