From: Simon Marchi <simon.marchi@polymtl.ca>
To: Weimin Pan <weimin.pan@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH PR gdb/22736] [aarch64] gdb crashes on a conditional breakpoint with cast return type
Date: Sun, 27 May 2018 03:42:00 -0000 [thread overview]
Message-ID: <af06191ac426ad2b74988803d51d1685@polymtl.ca> (raw)
In-Reply-To: <1527290419-17631-1-git-send-email-weimin.pan@oracle.com>
On 2018-05-25 19:20, Weimin Pan wrote:
> Don't call language_pass_by_reference() with function that has no
> return type.
>
> Only call language_pass_by_reference(), which returns whether or not an
> additional initial argument has been given, when return_type is not
> NULL
> in function aarch64_push_dummy_call().
Hi Weimin,
Since Pedro's patch that makes GDB not assume that the return type of
functions without debug info is int:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=7022349d5c86bae74b49225515f42d2e221bd368
I think we will always know the return type of the function. Either
it's in the debug info or it's provided by the user. In
call_function_by_hand_dummy, if the debug info doesn't provide the
return type of the function, we use the type of the user-provided cast:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/infcall.c;h=cd3eedfeeb712b27234a68cf8af394558ce4f57d;hb=cd3eedfeeb712b27234a68cf8af394558ce4f57d#l870
I think the default_return_type could be passed down to
gdbarch_push_dummy_call and used the same way, so that we always have a
return type.
Also, could you add a test case for this? I was able to create a simple
C++ (not C) program made from an object file built with no debug info:
int returns_two ()
{
return 2;
}
and one built with debug info:
int returns_two();
void func()
{
}
int main()
{
func();
return 0;
}
Putting this breakpoint and running crashes GDB:
(gdb) b func if (int)returns_two() == 2"
Thanks,
Simon
next prev parent reply other threads:[~2018-05-26 1:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 0:59 Weimin Pan
2018-05-27 3:42 ` Simon Marchi [this message]
2018-05-29 17:43 ` Wei-min Pan
2018-05-29 21:37 ` Simon Marchi
2018-05-30 0:29 ` Weimin Pan
2018-05-29 17:46 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2018-03-01 17:03 Alan Hayward
2018-03-02 3:32 ` Joel Brobecker
2018-03-02 12:09 ` Alan Hayward
[not found] ` <CAH=s-PP-Xy7TrP-0zKCuA2X4A8Xgx_gHNvYewm41LPs7ZZJniA@mail.gmail.com>
2018-03-02 14:05 ` Alan Hayward
2018-03-02 15:18 ` Joel Brobecker
2018-03-05 15:57 ` Alan Hayward
2018-03-05 16:45 ` Pedro Alves
2018-03-07 11:10 ` Alan Hayward
2018-03-09 8:51 ` Joel Brobecker
2018-03-09 16:04 ` Pedro Alves
2018-03-09 16:44 ` Yao Qi
2018-03-09 19:11 ` Alan Hayward
2018-03-02 10:07 ` Yao Qi
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=af06191ac426ad2b74988803d51d1685@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=weimin.pan@oracle.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