From: Elena Zannoni <elena.zannoni@oracle.com>
To: frysk <frysk@sourceware.org>
Subject: minutes 20070509
Date: Wed, 09 May 2007 15:28:00 -0000 [thread overview]
Message-ID: <4641E143.7050304@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: frysk-20070509 --]
[-- Type: text/plain, Size: 2699 bytes --]
Phil, Sami, Mike, Nurdin, Kris, Elena, Rick, Stan, Tim, Andrew
Rick: run executable, have terminal window, can assign stdin/out/err to
terminal to display output of program. Will add a button to allow this
to be on/off. Will it be possible to "unlock" std in out err from the
terminal as well? Possibly.
Console window, where you can run commands. Rewrite some menus, add
processes manipulation to top of window (with right button), also add
the action as a menu items (detach, abort, etc).
How do we do wrt the original goals/features of the project for source
window? Missing breakpoints (mike tim working on this) otherwise
pretty much most of functionality is there.
No good way to attach to a running process once you have the source
window open. Next thing to work on.
Mike: state machine, implementing breakpoint for the source windows,
and general bug fixing for the source window.
Assembly in source window is still at the same point, nobody is
working ont hat right now.
Register window, memory window, assembly window: need to look at 64bit
support, lower level is going to be wherer most work is needed. Kris.
Register window said to be working ok on 64 bit mode, Phil used that
during his corefile work.
Phil: corefile, relocatable/PIE. Solib handling. For GUI the only
extension is to specify "corefile" at the beginning of the session.
The rest should be transparent to the user.
Sami: bugs in monitor, and little fixes. No new features. Fixing bugs
in ftrace. Starting to look at Stack backtraces using debug info.
Nurdin: libunwind working now, good speed for remote frame. Cross
unwinding should be possible for 32 bit on 64 bit platforms as soon as
remote frame is "turned on", which will happen soon.
Tim: got the run and attach to stop at first instruction reliably. So
you can set any bps now. Setting bp in shlibs (before they are loaded)
is next.
Stan: started on Unions, wich is pretty much the last type left.
fhpd-> tried to add the "list" functionality. Similar to gdb but no
equivalent to "list -" in gdb. List function within a file is not
there yet, equivalent to "list file.c:foo". Trying to finish the
c-types first. Location expression is relatively simple. Simple
register locations. Need to handle more complex expressions.
Andrew: eliminated the ptrace thread from frysk.
Other:
Please, look at the test coverage, it's now more detailed and there
are big areas that are not tested.
Andrew noticed a bug at startup, Sami looking at it. Occurred between
May 1 and May 4. http://sourceware.org/bugzilla/show_bug.cgi?id=4474
One new person is starting on Frysk from ORCL: Pearly Zhao.
Next week meeting --> GUI: Tim and breakpoints.
reply other threads:[~2007-05-09 15:06 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=4641E143.7050304@oracle.com \
--to=elena.zannoni@oracle.com \
--cc=frysk@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).