Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 3/3] btrace, vdso: add vdso target sections
Date: Tue, 20 May 2014 14:10:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B230C16F3D8@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <537B4D25.3000303@redhat.com>

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Tuesday, May 20, 2014 2:40 PM


> > +  sections = NULL;
> > +  sections_end = NULL;
> > +  make_cleanup (xfree, sections);
> 
> This will always xfree NULL.  You either want:
> 
>  make_cleanup (free_current_contents, &sections);

That's what I wanted.  Thanks!


> 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.

add_target_sections copies the sections.


> > +# 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.

I overlooked that.  Sorry.

Regards,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052


  reply	other threads:[~2014-05-20 14:10 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 3/3] btrace, vdso: add vdso target sections Markus Metzger
2014-05-20 13:16   ` Pedro Alves
2014-05-20 14:10     ` Metzger, Markus T [this message]
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: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=A78C989F6D9628469189715575E55B230C16F3D8@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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