From: Andrew Cagney <cagney@redhat.com>
To: frysk@sourceware.org
Subject: Re: frysk ui meeting 2007-07-18 9:30 US east coast time
Date: Wed, 25 Jul 2007 13:27:00 -0000 [thread overview]
Message-ID: <46A74FD8.6060803@redhat.com> (raw)
In-Reply-To: <469D089A.5050002@redhat.com>
Display:
[mark posted the log from the terminal window]
Bugs found; none were display related!
bug#1 break command syntax (existing bug)
Should be <<break #23>> and not <<break @23>>
bug#2 In list command, where am i?
Vis:
(fhpd) list
10 asdf
11 bdf
12 ggh
13 uuh
(fhpd)
which line; (pick this one up this week with the disassembler)
bug#3 mixed output [mcvet]
(fhpd) go
Breakpoint at 10 hit
where is the prompt to indicate that the user has control again and
there isn't any more output
bug#4 4747
Panic some times when stepping.
bug#5 Tie the displayed PID to the session's task/proc ID [timoore]
----
Ideas: for display
-- extend to include dynamic display; for instance:
display $pc -format iinstruction
bug#6 deleted breakpoints not deleted
Apparently they only get disabled.
bug#7 no notification when task exits
---
Idea's for location syntax:
-> can it be extended to include column number vis #LINE#COL
-> way to specify an address
----
Round table:
Mark:
-> writing up documentation on ptrace/stepper
-> finishing instruction parser framework
-> memory bug 4761
-> memory access optimization 4760
-> follow up with 4747
Adam:
-> demo of display
-> will be tieing up loos ends
Tim:
-> working on HPD's proc/task syntax (dusting off the cobwebs)
Mike:
-> Looking at parser and source window bugs
-> chasing breakpoint bugs in stepper
Nurdin:
-> implemented better dwfl cache; refreshes instead of re-opens dwfl
after stop
-> disassembler in fhpd
Teresa:
-> utility to display required debug info
-> has script listing debug info to install working
Sami:
-> Fixing problems with displaying variables
-> Finished printing variables on stack
-> back to chasing problems with getting correct scope information from dwfl
Cagney:
-> ongoing cleanups
-> looking for dwfl memory leeks
Kris:
-> looking at documentation
-> looking to modify test system to recover from kernel crashes (more
robust)
-> working through memory window bugs
Phil:
-> makin corefile stuff more robust and rounding it out
Rick:
-> More source window issues with existing parser; bash is especially nasty.
---
Next week: disassembler, fstack? fdebuginfo?
Andrew Cagney wrote:
> (contact me for dial in info, in North America it's a free call)
>
> This week we're going to look at the "display" stuff adam has been
> working on. In particular, what it is and how it can be used :-)
>
> All welcome.
>
> Andrew
>
prev parent reply other threads:[~2007-07-25 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 18:20 Andrew Cagney
2007-07-18 8:40 ` Mark Wielaard
2007-07-25 13:27 ` 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=46A74FD8.6060803@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).