From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] btrace, vdso: add vdso target sections
Date: Fri, 16 May 2014 13:12:00 -0000 [thread overview]
Message-ID: <53760BDF.2080500@redhat.com> (raw)
In-Reply-To: <1396601586-24380-1-git-send-email-markus.t.metzger@intel.com>
Hi Markus,
Sorry for the delay...
Looks largely fine, but ...
On 04/04/2014 09:53 AM, Markus Metzger wrote:
> @@ -131,6 +133,27 @@ symbol_file_add_from_memory (struct bfd *templ, CORE_ADDR addr,
> from_tty ? SYMFILE_VERBOSE : 0,
> sai, OBJF_SHARED, NULL);
>
> + if (add_sections)
> + {
...
Why is this conditional? Why not add the sections if the symbols are
added manually with add-symbol-file-from-memory? The use case for the
command was originally exactly to add the vdso's symbols to GDB.
> + }
> + }
> +
> /* This might change our ideas about frames already looked at. */
> reinit_frame_cache ();
>
> @@ -159,7 +182,7 @@ add_symbol_file_from_memory_command (char *args, int from_tty)
> error (_("Must use symbol-file or exec-file "
> "before add-symbol-file-from-memory."));
>
> - symbol_file_add_from_memory (templ, addr, 0, NULL, from_tty);
> + symbol_file_add_from_memory (templ, addr, 0, NULL, 0, from_tty);
> +# trace the test code
> +gdb_test_no_output "record btrace"
> +gdb_test "next"
Please add a pattern that makes sure the "next" actually
finished successfully.
> +
> +# start replaying
> +gdb_test "reverse-stepi"
Likewise.
> +
> +# disassemble the code around the current PC
> +gdb_test "disassemble \$pc, +10" [join [list \
> + ".*" \
> + "End of assembler dump\." \
> + ] "\r\n"]
What is the error one gets without the fix? Doesn't
GDB say "End of assembler dump" in that case too?
--
Pedro Alves
next prev parent reply other threads:[~2014-05-16 13:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:53 Markus Metzger
2014-04-22 14:32 ` Metzger, Markus T
2014-04-22 14:39 ` Pedro Alves
2014-05-16 13:12 ` Pedro Alves [this message]
2014-05-19 8:07 ` Metzger, Markus T
2014-05-19 11:30 ` Metzger, Markus T
2014-05-19 21:41 ` Pedro Alves
2014-05-20 6:40 ` Metzger, Markus T
2014-05-20 11:12 ` Pedro Alves
2014-05-20 11:16 ` Metzger, Markus T
2014-05-20 17:15 ` [PATCH] Make the dcache (code/stack cache) handle line reading errors better Pedro Alves
[not found] ` <A78C989F6D9628469189715575E55B230C16FA4E@IRSMSX104.ger.corp.intel.com>
2014-05-21 9:45 ` [PATCH v2] " Pedro Alves
2014-05-21 11:29 ` Metzger, Markus T
2014-05-19 17:22 ` [PATCH] btrace, vdso: add vdso target sections 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=53760BDF.2080500@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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