From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/3] btrace, vdso: add vdso target sections
Date: Tue, 20 May 2014 13:16:00 -0000 [thread overview]
Message-ID: <537B4D25.3000303@redhat.com> (raw)
In-Reply-To: <1400587236-18836-3-git-send-email-markus.t.metzger@intel.com>
Thanks.
On 05/20/2014 01:00 PM, Markus Metzger wrote:
> @@ -92,6 +92,7 @@ symbol_file_add_from_memory (struct bfd *templ, CORE_ADDR addr,
> struct section_addr_info *sai;
> unsigned int i;
> struct cleanup *cleanup;
> + struct target_section *sections, *sections_end, *tsec;
>
> if (bfd_get_flavour (templ) != bfd_target_elf_flavour)
> error (_("add-symbol-file-from-memory not supported for this target"));
> @@ -131,6 +132,22 @@ symbol_file_add_from_memory (struct bfd *templ, CORE_ADDR addr,
> from_tty ? SYMFILE_VERBOSE : 0,
> sai, OBJF_SHARED, NULL);
>
> + sections = NULL;
> + sections_end = NULL;
> + make_cleanup (xfree, sections);
This will always xfree NULL. You either want:
make_cleanup (free_current_contents, §ions);
or move the cleanup to within the if/then block. You also need
to make sure to discard the cleanup on success.
Or, better yet, not install a cleanup at all? build_section_table
allocates the memory, and then the array is passed directly to
add_target_sections, which can be seen as a transfer of ownership.
If something throws after that call, we don't want the sections be
be simply xfree'd as that'd leave dangling pointers in the target
sections table.
> +
> + if (build_section_table (nbfd, §ions, §ions_end) == 0)
> + {
> + /* Adjust the target section addresses by the load address. */
> + for (tsec = sections; tsec != sections_end; ++tsec)
> + {
> + tsec->addr += loadbase;
> + tsec->endaddr += loadbase;
> + }
> +
> + add_target_sections (&nbfd, sections, sections_end);
> + }
> +
> /* This might change our ideas about frames already looked at. */
> reinit_frame_cache ();
> +# capture the disassembly of gettimeofday while live debugging
> +set live_gettimeofday [capture_command_output "disassemble gettimeofday" ""]
> +
> +# trace the test code
> +gdb_test_no_output "record btrace"
> +gdb_test "next" "main\.2.*"
> +
> +# capture the disassembly of gettimeofday while replaying
> +gdb_test "record goto begin" "main\.1.*"
> +set replay_gettimeofday [capture_command_output "disassemble gettimeofday" ""]
I think these two capture_command_output calls generate duplicate
gdb.sum output ? That's why I had with_test_prefix in my suggestion.
--
Pedro Alves
next prev parent reply other threads:[~2014-05-20 13:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 12:01 [PATCH v2 1/3] btrace: control memory access during replay Markus Metzger
2014-05-20 12:00 ` [PATCH v2 2/3] test, gcore: move capture_command_output into lib/gdb.exp Markus Metzger
2014-05-20 12:27 ` Pedro Alves
2014-05-20 12:00 ` [PATCH v2 3/3] btrace, vdso: add vdso target sections Markus Metzger
2014-05-20 13:16 ` Pedro Alves [this message]
2014-05-20 14:10 ` Metzger, Markus T
2014-05-20 12:26 ` [PATCH v2 1/3] btrace: control memory access during replay Pedro Alves
2014-05-20 16:12 ` Eli Zaretskii
2014-05-21 6:10 ` Metzger, Markus T
2014-05-21 15:12 ` Eli Zaretskii
2014-05-22 6:12 ` Metzger, Markus T
2014-05-22 14:58 ` Eli Zaretskii
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=537B4D25.3000303@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