Re: [Valgrind-valkyrie-dev] valkyrie-1.20

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

Hi Enrique,

Sorry it's taken so long to get back to this. We're finally pushing Valkyrie 
forward - it should be ready for a beta release coming monday.

Couple of questions about your findings...

1. configure does give options for setting the document install directory:
--docdir, --htmldir
But it seems these don't work! I'll try to get them working.
Assuming I can fix this, is this sufficient?

2. Can you still reproduce this? If so, please run from the commandline, and 
send me:
 - anything interesting on stdout/err
 - a copy of the relevant temporary generated xml file in ~/.valkyrie/logs/
   (this is auto-deleted when you close valkyrie, so make a copy of the latest 
file before closing).

3. Save Log is disabled? You mean when the error of (2) is given? I've changed 
the message slightly to say 'close this dialog, and then save log'. Does this 
solve this issue, or do I not understand?

4. Very strange... If there's an error such as dir not writeable, you're 
always given the chance to try again in a different place...
The text "Save failed" doesn't exist in the code. Can you reproduce this and 
tell me _exactly_ what happens?

5. Fixed.

Thanks for your feedback!
Cerion


On Tuesday 25 Dec 2007, you wrote:
> Hi,
>
> I packaged Valkyrie-1.2.0 for Slackware 12/DroplineGnome 2.20.  The
> following configuration was applied:
> prefix = /usr
> sysconfdir = /etc
> localstatedir = /var
>
> Documentation has been moved to /usr/doc/valkyrie-1.2.0/html.
>
> These are my observations and errors encountered thus far:
>
> 1 The path for the Help contents are hard-coded to /usr/doc. Since
> documentation has been moved, the
>   docs are not visible unless the Helpviewer is pointed to the right
> files. There is no way also to set paths.
>
> 2 Valkyrie's Valgrind fails to run on any binary I pointed it to but not
> when I used Valgrind alone. Error
>   messages are:
>
>   XML Parse error
>   Valgrind XML output is incomplete
>
>   Run error
>   Process exited with return value 1. This is likely to simply be the
> client program return value. If, however,
>   you suspect Valgrind itself may have crashed, please 'Save Log' and
> examine for details.
>
> 3 "Save Log" is disabled.
>
> 4 On exit, the Valkyrie prompts to save the output or not. When I click
> "Save", a file dialog opens. I entered
>   the name of the binary file I was testing then another error says
> "Save failed". So I discarded the output.
>
> 5 I also changed the  path on where to save the output but the save
> functionality seems to be hard-coded also
>   to /home/<acct>/.valkyrie/logs.
>
> I am a heavy Valgrind user as the reason I am attracted to Valkyrie. I
> was hoping this app will save me some
> time keeping track of Valgrind's output. I also hope that the feedbacks
> may help you in improving the software.
>
> Merry Christmas!