Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.btrace/*.exp: Make test names unique
Date: Fri, 07 Oct 2016 13:04:00 -0000	[thread overview]
Message-ID: <14c7b2a9e5600081174e94268de433f4@simark.ca> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B233FFE39A9@IRSMSX104.ger.corp.intel.com>

On 2016-10-07 03:42, Metzger, Markus T wrote:
>> -----Original Message-----
>> From: Simon Marchi [mailto:simon.marchi@ericsson.com]
>> Sent: Thursday, October 6, 2016 4:32 PM
>> To: Metzger, Markus T <markus.t.metzger@intel.com>; gdb-
>> patches@sourceware.org
>> Subject: Re: [PATCH] gdb.btrace/*.exp: Make test names unique
> 
> Hi Simon,
> 
>> >> This patch makes the btrace test names unique.  I was trying to
>> >> understand why rn-dl-bind.exp fails on my machine, and saw that it
>> >> failed at test "next".  Given that there are multiple "next" in that
>> >> test, it's hard to know which one doesn't work.
> [...]
>> Here's the gdb.log, if it can help you.
>> 
>> http://paste.ubuntu.com/23284745/
> 
> Thanks for sharing the log.  It does help.
> 
> You don't have debug information installed, which makes things more
> difficult for GDB.  The current tail-call detection heuristic is too 
> aggressive
> if there are no symbols available.
> 
> I posted a patch some time ago to make it less aggressive in this case:
> https://sourceware.org/ml/gdb-patches/2016-07/msg00277.html
> 
> This fixes (or hides, if you prefer) the issue you're seeing.  I don't 
> want to
> rule out that there might be other cases where we get the call stack 
> wrong
> if we don't have symbols available.
> 
> Let me ping again for this patch series.

Ok.

I have libc's debug symbols installed in /usr/lib/debug, but by default 
(without any --prefix) gdb looks in /usr/local/lib/debug, so it doesn't 
find it.  If I add a "set debug-file-directory /usr/lib/debug" at the 
beginning of the test, it passes.  It also passes with your patch 
series.

I will send a v2 of this patch when I have some free time.

Thanks!


      reply	other threads:[~2016-10-07 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 19:17 Simon Marchi
2016-10-06  8:44 ` Yao Qi
     [not found] ` <A78C989F6D9628469189715575E55B233FFE3504@IRSMSX104.ger.corp.intel.com>
2016-10-06 14:32   ` Simon Marchi
2016-10-07  7:43     ` Metzger, Markus T
2016-10-07 13:04       ` Simon Marchi [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=14c7b2a9e5600081174e94268de433f4@simark.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=simon.marchi@ericsson.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