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@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH] testsuite: disable break-interp.exp for Arm buildbot
Date: Thu, 15 Aug 2019 17:49:00 -0000	[thread overview]
Message-ID: <3836a7be-d1d4-3b21-6a2b-c98e41bcf52b@redhat.com> (raw)
In-Reply-To: <6B4E82F7-FCBE-46CC-8769-99C615D80F7E@arm.com>

On 8/12/19 4:53 PM, Alan Hayward wrote:

> Agreed. It’s not quite that simple - the failures happen in cases where there
> is no debug (eg BINprelinkNOdebugNOpieNO), so there is nowhere I can place
> a breakpoint.

Even if you have no debug info, you should still be able to put a breakpoint
on functions.  GDB knows the functions exist from the ELF symbol tables (minsyms):

 Reading symbols from testsuite/outputs/gdb.base/break-interp/break-interp-BINprelinkNOdebugNOpieNO...
 (No debugging symbols found in testsuite/outputs/gdb.base/break-interp/break-interp-BINprelinkNOdebugNOpieNO)
 (gdb) b main
 Breakpoint 1 at 0x40074b
 (gdb) 

Thanks,
Pedro Alves


      reply	other threads:[~2019-08-15 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  9:21 Alan Hayward
2019-08-09 17:22 ` Pedro Alves
2019-08-12 15:53   ` Alan Hayward
2019-08-15 17:49     ` Pedro Alves [this message]

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=3836a7be-d1d4-3b21-6a2b-c98e41bcf52b@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