From: Andrew Cagney <cagney@redhat.com>
To: frysk@sourceware.org
Subject: minutes 2007-07-11 at 9:30 east
Date: Wed, 11 Jul 2007 16:25:00 -0000 [thread overview]
Message-ID: <46950488.3090700@redhat.com> (raw)
In-Reply-To: <4693C37B.80007@redhat.com>
Technical discussion: cni vs jni
See and please follow up the e-mail:
http://sources.redhat.com/ml/frysk/2007-q3/msg00084.html
Round Table (Ordered roughly by last initial of first name):
Teresa:
Working on a mechanism to identify debug that is missing.
E.x.: given /bin/bash, that /usr/lib/debug/usr/bin/bash.debug and hence
bash-debuginfo should be installed
Current code is calling an elfutils find-debuginfo method directly;
investigating instead modeling things more after the builder-pattern
where elfutils would notify (call-back) frysk of the debug-info it is
looking at.
[side bar: roland's indicated that the code is under review; firstly
making mechanisms that simplify the task of frysk implementing the
debug-info call back function (e.g., making a crc-check method
available); and secondly exploring more efficient ways of confirming
that the debug info matches.]
Sami:
Printing values of variables in a stack frame. ezannoni asked if this
was hpd specific, sami answered that it was the oposite, removing hpd
specific assumptions from the existing code. Has one known 64-bit bug
remaining.
Mark:
Fixing problem where inserted breakpoints are visible when examining
memory contents - users don't expect to see breakpoint instructions in
their code. Adding a Task.getRawMemory which will contain what is
really in memory vs getMemory which is what the user thinks is there.
Rick:
More work cleaning up the cdtparser - current parser doesn't handle
macros well; worked around.
Other misc gui fixes.
Re-investigating option of moving to the CDT's latest parser; last time
this was investigated it was determined that it wasn't technically
possible as the parser had been heavely embedded into the CDT.
Working on moving the session concept out of the gui and into the core
so that it can be shared with the HPD.
Phil:
Adding x86-64 core-file tests so that code exercised on x86.
Conducting review of current fcore code.
[side bar: see enable 32-X-64 tests
http://sources.redhat.com/ml/frysk/2007-q3/msg00088.html ]
Tim:
Task/Proc stuff of HPD; for instance a Manager to assign each task/proc
HPD numbers. E.g., 0.0 is the first processes first task.
Cagney asked where the code is being added - frysk.rt - cagney noted
that that frysk.rt code eventually migrates to a more permanent home
(e.g., frysk.stack, frysk.debuginfo, ...).
Adam:
Improving robustness of display command; which in turn means adding more
action-point related commands to the HPD.
cagney:
Avoiding blockades.
Tracking down memory smash problems in dwfl/elf.
(Was trying to clean up the exception throw/catch code as often catch
code was discarding, instead of re-throwing, exceptions)
[Sidebar: dwfl/elf bindings have memory corruption problems; for
instance, when the object returned by DwflModule.getElf is freed it
could close out the dwfl's elf object.
Apologies: Stan, Chris, Kiris, Nurdin, Mike.
prev parent reply other threads:[~2007-07-11 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 17:35 meeting " Andrew Cagney
2007-07-11 12:08 ` Mark Wielaard
2007-07-11 16:25 ` 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=46950488.3090700@redhat.com \
--to=cagney@redhat.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).