From: Elena Zannoni <elena.zannoni@oracle.com>
To: frysk <frysk@sourceware.org>
Subject: minutes ui meeting 20070321
Date: Wed, 21 Mar 2007 15:07:00 -0000 [thread overview]
Message-ID: <4601488E.2030006@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: frysk-20070321 --]
[-- Type: text/plain, Size: 1610 bytes --]
Attendees:
Elena, Mark, Tim, Stan, Nurdin, Mike, cagney, Rick, Phil, Sami
fhpd demo (driven by script): commands shown were: list, help
(improved, as now you can get help on a specific command), up and
down, print, where, quit, assign.
Run on non-optimized version of program: works ok on C example program.
Run on optimized version of program: doesn't find variables correctly
quite yet.
Caches dwarf info as it is retrieved/used.
Tab completion for help was added. It now adds a space after the
command name that was completed, so user can type options. Also does
completion on things from the symbol table.
"print in<TAB>" caused exception.
"break 185"
"break"
caused another exception
break @file@lineno
assign int_21 0
caused a null pointer exception
break @/tmp/hpd.c@185
caused a null pointer exception
in this case breakpoint specified before specifying the program to run
fhdp on.
syntax was changed: cagney asks for justification from Tim: syntax
specify a # but parser interprets that as a comment, so it was changed
to @. Will be rectified once parser is fixed.
"break func_2, go, where" sequence works
Info printed when program stops at a breakpoint is being reworked to
be more legible.
where does the program stop if you say "run <program>". Not clear,
behavior seems to vary.
list command on assembly program: arrayindexoutofbounds exception
generated
Observers: Andrew and Sami discussed (private discussion) that the
observers/process picker workflows need to be simplified. Was the
design reviewed on the list? Not yet. Please post the ideas for
everybody to understand.
next reply other threads:[~2007-03-21 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 15:07 Elena Zannoni [this message]
2007-03-21 15:47 ` Sami Wagiaalla
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=4601488E.2030006@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).