public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: python.exp: filename functions FAIL
Date: Fri, 13 Aug 2010 15:34:00 -0000	[thread overview]
Message-ID: <20100813153444.GA29732@host1.dyn.jankratochvil.net> (raw)

Hi Phil,

getting 
	FAIL: gdb.python/python.exp: Test decode_line current locationn filename
	FAIL: gdb.python/python.exp: Test decode_line python.c:26 filename
	FAIL: gdb.python/python.exp: Test decode_line func1 filename
on x86_64-fedora14snapshot-linux-gnu (but even on fedora13 etc.).

The problem is the testcase gets compiled as:
	< c>   DW_AT_producer : GNU C 4.5.0 20100716 (Red Hat 4.5.0-3)
	<11>   DW_AT_name     : ./gdb.python/python-sl.c        
	<15>   DW_AT_comp_dir : /home/path/to/gdb-clean/gdb/testsuite   
while gdb uses
	result = PyString_FromString (symtab->filename);
and expects
	gdb_test "python print symtab\[1\]\[0\].symtab" "gdb/testsuite/gdb.python/python.c.*" "Test decode_line python.c:26 filename"
but it gets
	python print symtab[1][0].symtab
	./gdb.python/python.c
	(gdb) FAIL: gdb.python/python.exp: Test decode_line python.c:26 filename

It is a larger GDB problem with compilation directory vs. relative filename
path (wrt same base names in multiple directories etc.).  I do not know
specifically why sometimes the directory is
/home/path/to/gdb-clean/gdb/testsuite and sometimes /home/path/to/gdb-clean .

Suggesting to use for Python always only the absolute filename provided by:
	char * 
	symtab_to_fullname (struct symtab *s)

This is the only easy way how to solve the same filename in multiple source
directories anyway.


Thanks,
Jan

                 reply	other threads:[~2010-08-13 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100813153444.GA29732@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).