Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH v3 3/3] Aarch64: Fix segfault when casting dummy calls
Date: Tue, 30 Oct 2018 17:40:00 -0000	[thread overview]
Message-ID: <b0dce043-8466-87ec-fbb4-93289267f3d8@redhat.com> (raw)
In-Reply-To: <728A5D57-584B-405D-8315-FA1687C32192@arm.com>

On 10/30/2018 05:09 PM, Alan Hayward wrote:
> 
> 
>> On 30 Oct 2018, at 16:31, Pedro Alves <palves@redhat.com> wrote:

>> So that's the real difference.  Shared vs non-shared is just
>> a kind of a red herring.  If you don't have debug info for
>> libstdc++, for example, then probably GDB won't know that the
>> no-debug-info program is a C++ program either.
>>
>> So please adjust your test to eliminate use of the shared
>> library, and build just the cmp3 source file without
>> debug info.
> 
> Will do.

Thinking a little bit more, the conditional breakpoint is also
kind of a red herring here.  What really matters is the infcall.

So the testcase could just do:

  (gdb) p (int) cmp3(word)

I'd simplify the testcase a little bit in that direction,
and call it gdb.cp/nodebug-infcall.exp, for example.

Note, the testcase should be gated with a 

 if [target_info exists gdb,cannot_call_functions] {

check.

Thanks,
Pedro Alves


  reply	other threads:[~2018-10-30 17:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 14:49 [PATCH v3 0/3] " Alan Hayward
2018-10-11 14:49 ` [PATCH v3 3/3] " Alan Hayward
2018-10-19 11:36   ` Pedro Alves
2018-10-23 16:08     ` Alan Hayward
2018-10-24 15:15       ` Pedro Alves
2018-10-29 11:58         ` Alan Hayward
     [not found]           ` <862cf8f4-9491-a1eb-251e-6c7c1ffffa6c@redhat.com>
2018-10-29 14:56             ` Alan Hayward
2018-10-29 18:13               ` Pedro Alves
2018-10-30 11:13                 ` Alan Hayward
2018-10-30 16:31                   ` Pedro Alves
2018-10-30 17:09                     ` Alan Hayward
2018-10-30 17:40                       ` Pedro Alves [this message]
2018-10-11 14:49 ` [PATCH v3 1/3] Use enum for return method for " Alan Hayward
2018-10-19 11:28   ` Pedro Alves
2018-10-11 14:49 ` [PATCH v3 2/3] Pass return_method to _push_dummy_call Alan Hayward
2018-10-19 11:31   ` Pedro Alves
2018-10-18  9:50 ` [PING][PATCH v3 0/3] Aarch64: Fix segfault when casting dummy calls Alan Hayward

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=b0dce043-8466-87ec-fbb4-93289267f3d8@redhat.com \
    --to=palves@redhat.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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