Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	       GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Uniquify test names from gdb.python/{py-objfile.exp,py-pp-registration.exp}
Date: Wed, 29 Jul 2015 10:36:00 -0000	[thread overview]
Message-ID: <55B8ACB3.8040607@redhat.com> (raw)
In-Reply-To: <1437772393-6739-1-git-send-email-sergiodj@redhat.com>

Hi Sergio,

This unfortunately caused regressions in the testsuite:

Running /home/pedro/gdb/mygit/build/../src/gdb/testsuite/gdb.python/py-objfile.exp ...
FAIL: gdb.python/py-objfile.exp: Get no-debug objfile file
FAIL: gdb.python/py-objfile.exp: Test owner of real objfile.
FAIL: gdb.python/py-objfile.exp: Add separate debug file file
FAIL: gdb.python/py-objfile.exp: Test owner of separate debug file
FAIL: gdb.python/py-objfile.exp: Test user-name of owner of separate debug file
FAIL: gdb.python/py-objfile.exp: print main with debug info
FAIL: gdb.python/py-objfile.exp: print lookup_objfile of separate debug file

> -gdb_py_test_silent_cmd "python objfile = gdb.objfiles()\[0\]" \
> +gdb_py_test_silent_cmd "python objfile = gdb.s()\[0\]" \

Looks like a typo snuck in here.

Breakpoint 1, 0x0000000000400594 in main ()
(gdb) python objfile = gdb.s()[0]
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: 'module' object has no attribute 's'
Error while executing Python code.
(gdb) FAIL: gdb.python/py-objfile.exp: Get no-debug objfile file

>      "Get no-debug objfile file" 1

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-07-29 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1437772393-6739-1-git-send-email-sergiodj@redhat.com>
2015-07-28 21:40 ` Sergio Durigan Junior
2015-07-28 22:25   ` Pedro Alves
2015-07-29 10:36 ` Pedro Alves [this message]
2015-07-29 14:21   ` Sergio Durigan Junior
2015-07-29 14:34     ` Pedro Alves

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=55B8ACB3.8040607@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.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