From: Igor Kovalenko <garrison@mail.ru>
To: gdb-patches@sources.redhat.com
Subject: Re: Patch: Handle relative paths in .debug_line
Date: Fri, 01 Oct 2004 18:23:00 -0000 [thread overview]
Message-ID: <415DA139.6010309@mail.ru> (raw)
In-Reply-To: <415B5898.1020203@mail.ru>
I'm willing to devote some time to this problem, as it prevents me from
doing some necessary c++ debugging. So the question is what is currently
more necessary to have this problem fixed:
- Beat the testsuite into accepting one of available patches (e.g. by teaching
the suite about dwarf2 case or teaching patches to pass the testsuite)
- Have a test case for handling relative paths with dwarf2
Me wrote:
>
> Also I looked at regressions - this patch makes approximately the same
> number
> of failures as original relative paths patch. Test case gdb.base/unload.exp
> might show the reason - there seems to be a problem in handling relative
> paths
> within regression testing scripts:
>
> Running ../../../gdb-dejagnu/gdb/testsuite/gdb.base/unload.exp ...
> ERROR: couldn't open
> "../../../gdb-dejagnu/gdb/testsuite/gdb.base/../../../gdb-dejagnu/gdb/testsuite/gdb.base/unloadshr.c":
>
> no such file or directory
> FAIL: gdb.base/unload.exp: rerun to shared library breakpoint
>
The same holds for disassemble failures, I've not checked others yet.
My failure list have:
+FAIL: gdb.base/commands.exp: breakpoint in bp_deleted_in_command_test
+FAIL: gdb.base/commands.exp: breakpoint in temporary_breakpoint_commands
+FAIL: gdb.mi/mi-disassemble.exp: data-disassemble file, line assembly mixed
+FAIL: gdb.mi/mi-disassemble.exp: data-disassemble range assembly mixed
+FAIL: gdb.mi/mi-disassemble.exp: data-disassemble file, line, number assembly mixed
+FAIL: gdb.mi/mi-disassemble.exp: data-disassemble file, line, number (zero lines) assembly mixed
+FAIL: gdb.mi/mi-disassemble.exp: data-disassemble file, line, number (more than main lines) assembly mixed
+FAIL: gdb.mi/mi-file.exp: request path info of current source file (basics.c)
+FAIL: gdb.mi/mi2-disassemble.exp: data-disassemble file, line assembly mixed
+FAIL: gdb.mi/mi2-disassemble.exp: data-disassemble range assembly mixed
+FAIL: gdb.mi/mi2-disassemble.exp: data-disassemble file, line, number assembly mixed
+FAIL: gdb.mi/mi2-disassemble.exp: data-disassemble file, line, number (zero lines) assembly mixed
+FAIL: gdb.mi/mi2-disassemble.exp: data-disassemble file, line, number (more than main lines) assembly mixed
+FAIL: gdb.mi/mi2-file.exp: request path info of current source file (basics.c)
--
Kind regards,
Igor V. Kovalenko
next prev parent reply other threads:[~2004-10-01 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 0:40 Garrison
2004-09-30 0:49 ` Garrison
2004-10-01 18:23 ` Igor Kovalenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 23:31 Bryce McKinlay
2004-07-23 21:13 ` Jim Blandy
2004-07-23 23:54 ` Bryce McKinlay
2004-07-29 20:19 ` Jim Blandy
2004-07-29 20:54 ` Bryce McKinlay
2004-07-31 4:16 ` Jim Blandy
2004-07-31 19:23 ` Bryce McKinlay
2004-07-31 20:51 ` Andrew Cagney
2004-08-01 0:24 ` Michael Chastain
2004-09-14 19:53 ` Andrew Cagney
2004-09-14 20:09 ` Bryce McKinlay
2004-09-24 19:12 ` Andrew Cagney
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=415DA139.6010309@mail.ru \
--to=garrison@mail.ru \
--cc=gdb-patches@sources.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