From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: [RFC] Looking to fix AIX whatis-ptype-typedefs.exp
Date: Wed, 10 Jan 2024 07:21:25 +0000 [thread overview]
Message-ID: <CH2PR15MB3544C6E12813BBB0461F4EFAD6692@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Respected community members,
Hi,
In AIX we currently pass 28362 test cases and fail 2166 test cases while running gdb.base testsuite.
Of all the failures we are fixing one by one Whatis-ptype-typedefs.exp test case has 1062 failures.
The issue:-
When we try to check a type which is type casted then we are getting a syntax error. This looks like a parsing issue at first glance.
For example,
(gdb) whatis (void_typedef) void_typedef
A syntax error in expression, near `'.
Or
(gdb) whatis (func_ftype) int_typedef
A syntax error in expression, near `'.
(gdb) ptype (func_ftype) int_typedef
A syntax error in expression, near `'.
Whenever we typecast, we get this error message.
I am trying to understand why this happened while in other targets it runs smoothly. To fix the same for GDB community and AIX I need some guidance. Kindly help me with your knowledge and expertise.
Do we need to install any parsing package and need to configure GDB to use the same? Or is it got to with incorrect AIX specific code which is parsing the command. If it is the latter, then let me know the starting point to understand why this happened.
Hoping for a reply,
Have a nice day ahead.
Thanks and regards,
Aditya.
next reply other threads:[~2024-01-10 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:21 Aditya Kamath1 [this message]
2024-01-10 15:07 ` Tom Tromey
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=CH2PR15MB3544C6E12813BBB0461F4EFAD6692@CH2PR15MB3544.namprd15.prod.outlook.com \
--to=aditya.kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.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).