public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-128-ga8f1332
Date: Wed, 21 Oct 2009 10:49:00 -0000	[thread overview]
Message-ID: <20091021104901.6325.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  a8f1332f49206b314871fbdea50ab1045401a024 (commit)
       via  bc0b26aa958253192328bc4084ba367536fb4842 (commit)
       via  1adb61a4e1313b178f2db7d5ce766a505c073a24 (commit)
       via  bf043a5f9c9f807d670276b6c389bf5439245edb (commit)
       via  c42e2d2e1a9e8c09a435089ce351e1d36309dd9b (commit)
      from  96c57a86bb8d14b49b2e8b0ab8e9a044b2fadf42 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a8f1332f49206b314871fbdea50ab1045401a024
Merge: 96c57a86bb8d14b49b2e8b0ab8e9a044b2fadf42 bc0b26aa958253192328bc4084ba367536fb4842
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Oct 21 11:47:47 2009 +0200

    Merge branch 'unwind_robust'

commit bc0b26aa958253192328bc4084ba367536fb4842
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 20 17:08:57 2009 +0200

    Limit the number of call frame instructions we process in the unwinder.
    
    * runtime/unwind.c (processCFI): Fail if the number of instructions is
      larger than MAX_CFI (currently 512).

commit 1adb61a4e1313b178f2db7d5ce766a505c073a24
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 20 16:55:04 2009 +0200

    Make sure cie and fde end point to sane values in while doing unwind_frame.
    
    * runtime/unwind.c (unwind_frame): Check end read from cie or fde doesn't
      go passed end of unwind table.

commit bf043a5f9c9f807d670276b6c389bf5439245edb
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 20 13:55:15 2009 +0200

    Be paranoid about table size resolving cie_for_fde and fde_pointer_type.
    
    * runtime/unwind.c (cie_for_fde): Take table and table_len into account.
      (fde_pointer_type): Likewise.
    * runtime/unwind/unwind.h: Adjust function prototypes.

commit c42e2d2e1a9e8c09a435089ce351e1d36309dd9b
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 20 12:38:55 2009 +0200

    Add limit on unwind table size we accept.
    
    * translate.cxx (MAX_UNWIND_TABLE_SIZE): New define.
      (dump_unwindsyms): Check debug_len and eh_len against new limit.

-----------------------------------------------------------------------

Summary of changes:
 runtime/unwind.c        |   43 ++++++++++++++++++++++++++++++++++++-------
 runtime/unwind/unwind.h |    6 ++++--
 translate.cxx           |   11 +++++++++++
 3 files changed, 51 insertions(+), 9 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-10-21 10:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20091021104901.6325.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).