From: Tom Tromey <tom@tromey.com>
To: Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
"simon.marchi@efficios.com" <simon.marchi@efficios.com>,
Aditya Kamath1 <Aditya.Kamath1@ibm.com>,
Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
Sanket Rathi <sanrathi@in.ibm.com>
Subject: Re: [PATCH] Fix call functions command bug in 64-bit programs for AIX
Date: Wed, 16 Nov 2022 11:30:31 -0700 [thread overview]
Message-ID: <877czuu4zc.fsf@tromey.com> (raw)
In-Reply-To: <BY5PR15MB3540464A747BB9A3BC13C81DD6079@BY5PR15MB3540.namprd15.prod.outlook.com> (Aditya Kamath's message of "Wed, 16 Nov 2022 18:07:44 +0000")
>> It might not really be necessary to handle pointer and reference
>> types if those are always guaranteed to be word sized. But I
>> think enum, bool, and char types should be handled.
> You were right. Thank you for pointing out. I have attached the
> outputs below. It works fine now.
I didn't look at this too deeply, but it's worth noting that code
handling the marshalling of integers should also handle
TYPE_CODE_FIXED_POINT as well, as those are integers with a funny
name. There should be some Ada tests for this.
If you can't test Ada, I guess don't worry about it. I'm not 100% sure
the way you've written this will work for a fixed-point number.
> warning: (Internal error: pc 0x10000290 in read in psymtab, but not in symtab.)
This normally indicates a serious bug. Also I guess you must be using
stabs?
> BFD: /usr/lib/libc.a(/usr/lib/libc.a(shr_64.o)): wrong auxtype 0xff for storage class 0x2
> BFD: /usr/lib/libc.a(/usr/lib/libc.a(shr_64.o)): wrong auxtype 0xff for storage class 0x6b
These seem concerning.
thanks,
Tom
next prev parent reply other threads:[~2022-11-16 18:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 11:00 Aditya Kamath1
2022-11-08 13:30 ` Ulrich Weigand
2022-11-11 17:53 ` Aditya Kamath1
2022-11-14 15:54 ` Ulrich Weigand
2022-11-14 17:32 ` Aditya Kamath1
2022-11-14 18:19 ` Ulrich Weigand
2022-11-14 18:28 ` Aditya Kamath1
2022-11-14 18:43 ` Ulrich Weigand
2022-11-14 18:52 ` Aditya Kamath1
2022-11-14 19:10 ` Ulrich Weigand
2022-11-16 11:27 ` Aditya Kamath1
2022-11-16 15:15 ` Ulrich Weigand
2022-11-16 18:07 ` Aditya Kamath1
2022-11-16 18:30 ` Tom Tromey [this message]
2022-11-17 12:54 ` Ulrich Weigand
2022-11-24 17:56 ` Aditya Kamath1
2022-11-24 18:15 ` Tom Tromey
2023-04-14 7:38 ` [PATCH] Fix call functions command bug in 64-bit programs for AIX and PC read in psymtab-symtab warning Aditya Kamath1
2023-04-14 14:45 ` Tom Tromey
2023-04-17 13:08 ` Aditya Kamath1
2023-04-17 13:16 ` Aditya Kamath1
2023-04-18 10:12 ` Ulrich Weigand
2023-04-21 13:00 ` Aditya Kamath1
2023-04-24 15:44 ` Ulrich Weigand
2023-04-27 10:13 ` Aditya Kamath1
2023-04-27 12:23 ` Ulrich Weigand
2023-04-27 10:14 ` Aditya Kamath1
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=877czuu4zc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=sanrathi@in.ibm.com \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).