On Thu, Aug 14, 2008 at 08:14:25AM -0600, [EMAIL PROTECTED] wrote:
>
> > Doing gdb sessions in the build tree is pretty tricky because of all the
> > setup (e.g., setting environment variables) you have to do first. So I
> > don't
> > recommend it except for rare emergencies where you get errors i
On 2008-08-14 08:14-0600 [EMAIL PROTECTED] wrote:
> My problem is that I'm building RPM packages and so it's pretty much
> impossible to do the testing in the install tree. I'll work on a patch.
Thanks in advance, Orion. I suggest instead of using --debug, you use
--extra-verbose as the name of
> Doing gdb sessions in the build tree is pretty tricky because of all the
> setup (e.g., setting environment variables) you have to do first. So I
> don't
> recommend it except for rare emergencies where you get errors in the build
> tree but not the install tree. Furthermore, ctest doesn't have
On Wed, Aug 13, 2008 at 04:11:54PM -0700, Alan Irwin wrote:
> On 2008-08-13 22:13+0100 Andrew Ross wrote:
>
> > In principal I like the idea of being able to see the examples as they
> > are exectuted. I wonder whether the whole command line is necessary
> > though. Perhaps just echoing the exampl
On 2008-08-13 15:19-0600 Orion Poplawski wrote:
> Andrew Ross wrote:
>> In principal I like the idea of being able to see the examples as they
>> are exectuted. I wonder whether the whole command line is necessary
>> though. Perhaps just echoing the example name would suffice and would
>> prevent
On 2008-08-13 22:13+0100 Andrew Ross wrote:
> In principal I like the idea of being able to see the examples as they
> are exectuted. I wonder whether the whole command line is necessary
> though. Perhaps just echoing the example name would suffice and would
> prevent too much unnecessary clutter
Andrew Ross wrote:
> In principal I like the idea of being able to see the examples as they
> are exectuted. I wonder whether the whole command line is necessary
> though. Perhaps just echoing the example name would suffice and would
> prevent too much unnecessary clutter in the output? For testing
On Tue, Aug 12, 2008 at 03:45:39PM -0700, Alan Irwin wrote:
> On 2008-08-11 19:59-0700 Alan W. Irwin wrote:
>
> > On 2008-08-11 14:43-0600 Orion Poplawski wrote:
> >
> >> Wishlist: a verbose testing option that
> >> would output the actual command executed for each test.
>
> I have implemented a
On 2008-08-11 19:59-0700 Alan W. Irwin wrote:
> On 2008-08-11 14:43-0600 Orion Poplawski wrote:
>
>> Wishlist: a verbose testing option that
>> would output the actual command executed for each test.
I have implemented a proof of concept of this idea (revision 8636) for our C
examples. Please tr
On 2008-08-11 14:43-0600 Orion Poplawski wrote:
> Wishlist: a verbose testing option that
> would output the actual command executed for each test.
I get a similar result "by hand" by, e.g., putting the command
echo $index
inside the shell loop in plplot_test/test_ada.sh (or any of the other
s
10 matches
Mail list logo
