From: "Willem Hajenius" <willem.hajenius@ping.be>
To: <insight@sourceware.cygnus.com>
Subject: Bugs/Features
Date: Thu, 13 Sep 2001 12:27:00 -0000 [thread overview]
Message-ID: <000201c13c8a$82607f00$32285fc3@hajeniuscomp> (raw)
To the developers of the Cygnus Insight Debugger v5.0,
Your visual debugger is my all-time favorite! I use it in conjunction
with Dev-C++ and it performs excellent! However, I've found the following
bugs/remarks in your product that should deserve some attention:
* Please provide a window similar to the "Source is more recent than
executable"-dialog, with a "Don't show this in the future"-checkbox,
and an Preference setting to enable all disabled messages. (This is
often forgotten; as a consequence users become fearful to dismiss a dialog
'forever'.)
* The checkbox mentioned above doesn't work: the dialog keeps popping up
in future sessions.
* Also make the "i386 Architecture file may be incompatible with i386:intel
target"-message box dismissable. After hundreds of debugging sessions it
becomes
very annoying.
* Add a Preference option to completely expand or contract the compound
variables
in the Local Variables-window. This would prove very time-saving,
particularly
with complex data structures.
* (Not quite sure about the exact cause of this one) It appears that when
an array is (re)alloc'ed, it's representation in the Local Variables-window
is not updated. Consider the following code snippet:
struct rec
{
char c[5];
};
typedef struct rec foo;
int main()
{
foo* f;
f = (foo*) malloc (10);
f->c[9] = 'A';
free (f);
return 0;
}
This works perfectly well, yet the Local Variables-window doesn't indicate
that
'c' is now 10 characters large.
Please think about these issues.
Kind regards,
Alexander Hajenius.
next reply other threads:[~2001-09-13 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 12:27 Willem Hajenius [this message]
2001-09-13 13:08 ` Bugs/Features Keith Seitz
2001-09-13 16:53 ` Bugs/Features Tom Tromey
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='000201c13c8a$82607f00$32285fc3@hajeniuscomp' \
--to=willem.hajenius@ping.be \
--cc=insight@sourceware.cygnus.com \
/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).