From: "Marcin Kościelnicki" <koriakin@0x04.net>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/8] gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp
Date: Wed, 09 Mar 2016 17:27:00 -0000 [thread overview]
Message-ID: <56E05CF2.8020305@0x04.net> (raw)
In-Reply-To: <20160309172438.7ADA4C88E@oc7340732750.ibm.com>
On 09/03/16 18:24, Ulrich Weigand wrote:
> Marcin Kościelnicki wrote:
>
>> On powerpc64, foo/bar point to a function descriptor, not to function code.
>> Since there are no global labels pointing at the actual function code,
>> let's make our own.
>
>> with_test_prefix "tracing foo" {
>> - gdb_test "trace foo" ".*"
>> + gdb_test "trace *foo_start_lbl" ".*"
>
> Well, I'd have thought that "trace foo" should simply work as-is,
> otherwise, this isn't particularly user-friedly ...
>
> Is there a call to gdbarch_convert_from_func_ptr_addr missing
> somewhere in the trace code, maybe?
Don't worry, trace foo does work, but not for this particular test,
because of the way the fake DWARF is emitted: before, the DWARF covered
area from foo to foo_end_lbl, and thus a tracepoint set on foo worked
just fine. However, now the DWARF covers foo_start_lbl to foo_end_lbl -
and function entry point (which is where the tracepoint is) is not covered.
>
> Bye,
> Ulrich
>
next prev parent reply other threads:[~2016-03-09 17:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 16:35 [PATCH 0/8] Add regular tracepoint support for powerpc Marcin Kościelnicki
2016-03-06 16:35 ` [PATCH 4/8] gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp Marcin Kościelnicki
2016-03-09 17:24 ` Ulrich Weigand
2016-03-09 17:27 ` Marcin Kościelnicki [this message]
2016-03-09 17:35 ` Ulrich Weigand
2016-03-06 16:35 ` [PATCH 8/8] gdb: Add tracepoint support for powerpc Marcin Kościelnicki
2016-03-09 17:33 ` Ulrich Weigand
2016-03-09 17:48 ` Marcin Kościelnicki
2016-03-06 16:35 ` [PATCH 7/8] gdb.trace/entry-values.exp: Fixes for powerpc64 Marcin Kościelnicki
2016-03-09 17:29 ` Ulrich Weigand
2016-03-06 16:35 ` [PATCH 1/8] gdb: Add ax_pseudo_register_collect for powerpc Marcin Kościelnicki
2016-03-09 17:20 ` Ulrich Weigand
2016-03-06 16:35 ` [PATCH 2/8] gdb: Add gen_return_address " Marcin Kościelnicki
2016-03-09 17:20 ` Ulrich Weigand
2016-03-06 16:35 ` [PATCH 6/8] gdb.trace/tfind.exp: Force call via global entry point on ppc64le Marcin Kościelnicki
2016-03-09 17:26 ` Ulrich Weigand
2016-03-06 16:40 ` [PATCH 3/8] gdb/rs6000: Read backchain as unsigned Marcin Kościelnicki
2016-03-09 17:21 ` Ulrich Weigand
2016-03-06 16:40 ` [PATCH 5/8] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering Marcin Kościelnicki
2016-03-09 17:25 ` Ulrich Weigand
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=56E05CF2.8020305@0x04.net \
--to=koriakin@0x04.net \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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