From: Stan Cox <scox@redhat.com>
To: Frysk Hackers <frysk@sourceware.org>
Subject: minutes 2006-10-17
Date: Wed, 18 Oct 2006 14:43:00 -0000 [thread overview]
Message-ID: <1161182498.6539.163.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <45350F97.5010200@redhat.com>
Testing:
Chris looking at stopped process problem (210693) along with Roland
RHTS automatic tests can be run manually
Code Coverage (Stan,Andrew)
-action: simpler test for 210693 (Oct-20, cmoller)
-action: try out RHTS tests (Oct-20, cmoller)
-action: code coverage (Oct-20, scox)
Source View:
cdt parser bug fixing (Rick)
-perhaps actually a libgcj bug?
libiberty demangler and libiberty licensing
-action: demangler plan (Oct-20, stan)
Command Line Utilities:
first cut of fcore complete
gelf always uses 64 bit header
-should be able to get 32 bit corefile on a 64 bit machine
-currently elf headers look the same as gcore
Instead of panicing, detach process and let core continue to run.
-change attach,continue,stop,detach TO attach,detach
-add abandoning state like detach but 'worse'
-action: consider how to load core file (Oct-20, pmuldoon)
-action: Process detach (Oct-27, mcvet)
Core: backend/middle end
stepping is committed via a blocking observer
Tim looking at high level breakpoints
-action: Pick this up while Mark on vacation (Oct-27, npremji)
Java-GNOME:
Need these resolved:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209346
http://sourceware.org/bugzilla/show_bug.cgi?id=3116
http://bugzilla.gnome.org/show_bug.cgi?id=353298
-action: Resolve java-gnome problems (?, ?)
New ports:
IBM PPC libunwind status?
Ubuntu build problems
Documentation and demo workflow:
Nice to have: show workflows for debugging and monitoring
Documentation will use yelp, the gnome help system
-to what extent does it use gnome?
next prev parent reply other threads:[~2006-10-18 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 17:14 meeting 2006-10-17 Andrew Cagney
2006-10-18 14:43 ` Stan Cox [this message]
2006-10-19 2:17 ` minutes 2006-10-17 Wu Zhou
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=1161182498.6539.163.camel@multics.rdu.redhat.com \
--to=scox@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).