Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Rajendra SY <rajendra.sy@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [PR gdb/23095] Fixed test case to compile & run on FreeBSD
Date: Sat, 21 Apr 2018 14:59:00 -0000	[thread overview]
Message-ID: <0eae05d2f22d863db5b7b5b890a76a4a@polymtl.ca> (raw)
In-Reply-To: <CAMAnt0nkbMQ=xEo+Fv8tu9evbt1wHgU239XxWc4sNTuQ72vDKg@mail.gmail.com>

On 2018-04-20 23:10, Rajendra SY wrote:
> Problems:
> 1. linking -dl lib on FreeBSD platform
> 2. backtrace from ld-elf shows r_debug_state() instead of 
> _dl_debug_state()
> 
> Cause:
> 1. There is no dl library on FreeBSD platform test has to ignore 
> linking "-ldl"
> 2. The stop due to a shared library event shows backtrace frame #0
> function as r_debug_state()
> 
> Test passed:
> PASS: gdb.base/break-probes.exp: set stop-on-solib-events 1
> 
> gdb/ChangeLog:
> 2018-04-20  Rajendra SY  <rajendra.sy@gmail.com>
> 
>         PR gdb/23095
>         * gdb/testsuite/gdb.base/break-probes.exp:

Hi Rajendra,

Instead of conditionally adding -ldl in the test, it would be better to 
pass the "shlib_load" options to prepare_for_testing.  It will add the 
right flag depending on the platform.

It is handled here, from what I see it already considers freebsd:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/testsuite/lib/gdb.exp;h=4d48f5e3ad39967bba3ecf8cad5da5ea87f355c8;hb=HEAD#l3593

Can you try that?

The other part of the change (r_debug_state) is probably fine to keep 
there, because it's very specific to this test.

Simon


  reply	other threads:[~2018-04-21 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  3:11 Rajendra SY
2018-04-21 14:59 ` Simon Marchi [this message]
2018-04-22  1:31   ` Rajendra SY
2018-04-22 14:11     ` Simon Marchi
2018-04-22 15:33       ` Rajendra SY
2018-04-22 22:21         ` Simon Marchi

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=0eae05d2f22d863db5b7b5b890a76a4a@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=rajendra.sy@gmail.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