public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: Re: meeting 2008-03-04 9:30 us-east
Date: Wed, 05 Mar 2008 17:31:00 -0000	[thread overview]
Message-ID: <47CED88D.3030909@redhat.com> (raw)
In-Reply-To: <47CEAB9B.8070808@redhat.com>

    *    5876 [---, frysk-bugzilla@sourceware.org] -meeting 2008-03-04.
      <http://sourceware.org/bugzilla/show_bug.cgi?id=5876>
          o 5877 [---, swagiaal@redhat.com] -utilities should trace
            children by default.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5877>
          o 5878 [---, frysk-bugzilla@sourceware.org] -fexe can't find a
            shell script.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5878>
          o 5879 [---, frysk-bugzilla@sourceware.org] -(fhpd) list +10
            -- list next 10 lines.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5879>
          o 5880 [---, timoore@redhat.com] -following children in fhpd.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5880>
          o 5881 [---, frysk-bugzilla@sourceware.org] -breakpoint across
            exec. <http://sourceware.org/bugzilla/show_bug.cgi?id=5881>
          o 5882 [---, frysk-bugzilla@sourceware.org] -in
            StartClonedState.Blocked, got terminating.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5882>
          o 5883 [---, timoore@redhat.com] -break main, without any
            breakpoints.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5883>
          o 5884 [---, frysk-bugzilla@sourceware.org] -breakpoint across
            clone. <http://sourceware.org/bugzilla/show_bug.cgi?id=5884>
          o 5885 [---, frysk-bugzilla@sourceware.org] -Internal Error:
            frysk.debuginfo.VariableOptimizedOutException.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5885>
          o 5886 [---, frysk-bugzilla@sourceware.org]
            -frysk.stack.ErrorFrame class.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5886>
          o 5887 [---, frysk-bugzilla@sourceware.org] -always an inner
            most frame.
            <http://sourceware.org/bugzilla/show_bug.cgi?id=5887>
          o 5888 [---, cagney@redhat.com] -if the unwind fails, stop the
            step. <http://sourceware.org/bugzilla/show_bug.cgi?id=5888>


general discussion:

-> what should fcore do with -sysroot - does it even make sense?  yes
Consider pulling a process, running in a chrooted jail but from outside 
of the chroot:
      $ fcore -sysroot /path/to/chroot/jail 1234
while most of the information would be still drawn from /proc, 
executable information would be taken from the images within the 
chrooted jail.

-> existing bugs
Everone noticed that they had bugs they could now close

-> how to track meeting bugs where no action is intended
Choices were:
  - remove as meeting blockers
  - close/clone
  - assign to frysk-bugzilla@
consensus was on last one


      reply	other threads:[~2008-03-05 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 14:18 Andrew Cagney
2008-03-05 17:31 ` Andrew Cagney [this message]

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=47CED88D.3030909@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).