public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Elena Zannoni <elena.zannoni@oracle.com>
To: frysk <frysk@sourceware.org>
Subject: minutes 20070523
Date: Wed, 23 May 2007 15:24:00 -0000	[thread overview]
Message-ID: <46545537.5040102@oracle.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: frysk-20070523 --]
[-- Type: text/plain, Size: 1648 bytes --]

Mark, Phil, Rick, Andrew, Nurdin, Sami, Tim, Elena, Kris, Pearly.


Discussions about dwarf2 and how frysk internal data structures should
be, in order to minimize memory usage.

Other discussions wih Phil and Andrew, about proc.

Roundtable:

Andrew: refactoring of ptrace: right way to do it seems to be along
the lilnes of live process vs. dead process.

Sami: learning dwarf and working on unwinding

Stan: added union and tab completion on member names. Ran into
problem: tab completion was broken because of terminal
handling. Getting ready to move to c++.

Nurdin: Dwarfl callback to use proc get memory,

Tim: breakpoint manager and breakpoint, get breakpoints into
multiprocesses, from cli.

Phil: building a map for the corefiles. Hard problem.

Rick: console window in source window. Attach to running process from
source window, and getting terminal window in source window.

Mark: was sick and away for conference.

Kris: Tweaked the summary report email for the automated builds (as
can be seen on the list), reporting on changes from day to day (both
positive and negative).  Also been looking more at the 64-bit support
for the register/memory/disassembly windows.  Tracing code paths to
ensure support is consistent with 32-bit, and plan out new code needed
or code changes for anything requiring tweaking.

Pearly: as mentioned in the past meeting, she is still learning her
way around the code, so it will be a while before she can contribute.

Next week: Andrew will assign study questions on dwarf2, people will
come to the meeting with an answer, and explain to the others.
No GUI review, nothing to talk about in GUI-land.



                 reply	other threads:[~2007-05-23 15:04 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=46545537.5040102@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).