Re: [Valgrind-valkyrie-dev] sugesstions...

[Cerion Armour-B. <ce...@ke...>]

Thanks for the feedback Anton,

Very clear now what's going on with 3i,iii, cheers - I should be able to sort 
those out.
Thanks for the playback - good in principle, but I'm afraid I'd rather 
discourage this... screenshots and text should be enough. I don't like 
opening strange attachments, and the size makes it unsuitable for the dev 
list.

2. is somewhat tougher... I don't see a nice general way to solve this one. 
I'll ponder some more.

Cheers,
Cerion


On Monday 09 Jun 2008, Anton Dudarenko wrote:
> 1. Thanks!!!
> 2. Our sources sometimes became unavailable because sometimes servers which
> keep this files are turning off )))
> And in this case I would like to use my local version of code - so I have
> to use the path not from debug info but from my point of view. And so I
> want to still be able to open errors messages even from inaccessible files
> )) 3i Maybe you have a latest development build - not final available
> 1.2.0?? But in any way - I've created a small avi and a log-file - all is
> 7zipped - see attach.
> In this movie)) you can see all "bugs".
>
> In the beginning of movie I am showing to you 3i bug behavior.
> I am pressing but. "'Open|Close errors'" and only SCP and UNC was
> unfolded))
>
> After that I am showing to you behavior of but. "'Open|Close the selected
> item'" - bug 3iii - It becomes available ONLY if I was opening 1 tree node
> by mouse and selected some subitems(function`s call stack) in this tree
> node..
>
> After that I am again showing to you 3i bug BUT with some new unexpected
> behavior - I've closed all nodes by mouse but button still is still visible
> as pushed. Even when I opened/closed node by "arrow key" buttons from the
> keyboard.
>
> After that bug 3iii again was shown. Now I was used "arrow key" buttons
> from the keyboard. And a mouse again))
>
> Hope this will help)))
>
> -----Original Message-----
> From: Cerion Armour-Brown [mailto:ce...@ke...]
> Sent: Saturday, June 07, 2008 8:33 PM
> To: val...@li...
> Cc: Anton Dudarenko
> Subject: Re: [Valgrind-valkyrie-dev] sugesstions...
>
> Thanks for the feedback Anton.
>
> We're busy now fixing some bugs and supporting the latest valgrind
> release...
>
> 1. Fixed
> 2. I don't really understand why this is necessary: do you move your
> sources
>
> after building?
> 3i. ?! I can't reproduce this - can you send me the logfile pls?
> 3ii. Well spotted :-) I'll add it to the todo list
> 3iii. I don't understand what you mean, can you clarify?
> 4. I've added more options for the configure script - adding the
> functionality
> in the valkyrie options is too much work for now: maybe in the future :-)
>
> Regards,
> Cerion
>
> On Tuesday 03 Jun 2008, Anton Dudarenko wrote:
> > Your tool is simply excellent, but I would like to notice something in
> > its behaviour and to suggest improving it.
> >
> > 1. To include horizontal scrolling for a LOG window. Otherwise it is
> > impossible to see the full text of the memory check`s messages of an
>
> error.
>
> > 2. To include possibility to open on double click a file even if it is
> > certain by you as inaccessible. The obvious decision - simply to display
> > a inquiry window with the text "On the given way a file it is not
> > accessible - whether YOU wish to specify its place independently?" And if
> > the user
>
> has
>
> > specified it - to use the received way further and as consequence -
>
> already
>
> > at once to open an editor window with the specified file on the specified
> > line at double click...
> >
> > 3. To "cure" behaviour of buttons 'Open|Close errors' and 'Open|Close the
> > selected item'. In the current version they work not correctly.
> >
> > 3i. The first
> > command opens a tree only for SysCallParam and UnInitCondition nodes. The
> > others remain folded.
> >
> > 3ii. And it remains turned ON (the button visually is
> > pressed) even if I have folded after that all nodes by means of "arrow
>
> key"
>
> > buttons on the keyboard.
> >
> > 3iii.
> > The second command to become accessible to the chosen tree node of an
>
> error
>
> > messages only if this node has been preliminary opened and will fold
> > again by mouse or by means of "arrow key" buttons on the keyboard.
> >
> > 4. In a window of program properties at a field of editor choice well to
> > provide auto filling of a command line for 2-4 widespread editors
> >
> > gvim +%n
> >
> > vi +%n
> >
> > vimx +%n
> >
> > kate --line %n
> >
> > etc....
> >
> > And for the KATE editor it is necessary on one to reduce number of a line
> > on which it will be necessary to move in the opened editor. It is an
> > error of this editor itself that at the jump from a command line for the
> > line 5, for example, actually it passes on 6.