Re: [Valgrind-developers] tool-specific CLOs

[Tom H. <th...@cy...>]

In message <Pin...@re...>
        Nicholas Nethercote <nj...@ca...> wrote:

> On Wed, 7 Jan 2004, Tom Hughes wrote:
>
>> >> It wouldn't be hard to allow ./.valgrindrc and ~/.valgrindrc files, too,
>> >> which can contain (prefixed and non-prefixed) options, just like the
>> >> VALGRIND_OPTS var.
>> >
>> > I vote for this.
>>
>> Me to. It would be nice if it could handle spaces in option values
>> somehow as well - they are now handled in command line arguments
>
> Really?  Do any of the existing options handle them?  Does it require
> quoting?  Seems like knowing when an option ends and a command name begins
> is problematic if spaces are allowed, eg. in "--foo=bar baz" is "baz" part
> of the --foo option or the name of the executable?

No existing options require spaces, but the --db-command option that
is in my patch for bug 69489 does as the command to start the debugger
will normally include spaces.

For the .valgrindrc files it should be difficult if they expect one
option per line, for the env var some form of quoting would have to
be supported.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/