Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-23 Thread Noel Grandin
On 2012-07-23 09:27, Miklos Vajna wrote: So - I think this has been already mentioned in this thread, to just avoid the pain, the best is to run make check without DEBUGCCPUNIT=TRUE My point is that this used to work, and I'm pretty sure it's a bug in the make scripts, since it doesn't seem t

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-23 Thread Miklos Vajna
Hi Noel, On Fri, Jul 20, 2012 at 10:54:04AM +0200, Noel Grandin wrote: > Ping? > Anybody have any ideas? > This is driving me nuts during my testing. So - I think this has been already mentioned in this thread, to just avoid the pain, the best is to run make check without DEBUGCCPUNIT=TRUE, and

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-20 Thread Noel Grandin
Ping? Anybody have any ideas? This is driving me nuts during my testing. On 2012-07-11 13:25, Noel Grandin wrote: OK, I'm closer to figuring this one out. When I do this: $ DEBUGCPPUNIT=TRUE make -s check gdb executes the unit tests, but then, if everything went OK, GDB __doesn't quit__ I

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-11 Thread Noel Grandin
OK, I'm closer to figuring this one out. When I do this: $ DEBUGCPPUNIT=TRUE make -s check gdb executes the unit tests, but then, if everything went OK, GDB __doesn't quit__ I have to enter a "q" on the console. However, if there actually was an exception, then GDB correctly prints it out,

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Noel Grandin
On Tuesday, 10 July 2012, Michael Meeks wrote: > > On Tue, 2012-07-10 at 15:33 +0200, Noel Grandin wrote: > > It seems to be a general thing. Not specific to one test, they all > > pause, so I have to enter lots of "r" and "q" > > Sure - that is to let you do interactive debugging of the t

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Michael Meeks
On Tue, 2012-07-10 at 15:33 +0200, Noel Grandin wrote: > It seems to be a general thing. Not specific to one test, they all > pause, so I have to enter lots of "r" and "q" Sure - that is to let you do interactive debugging of the test :-) if you don't want that behaviour don't set that v

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Miklos Vajna
On Tue, Jul 10, 2012 at 03:33:24PM +0200, Noel Grandin wrote: > It seems to be a general thing. Not specific to one test, they all > pause, so I have to enter lots of "r" and "q" What usually do is: I run toplevel 'make check', then once I know what is the test I want to debug, I run something li

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Noel Grandin
On 2012-07-10 15:29, Michael Meeks wrote: On Tue, 2012-07-10 at 13:08 +0200, Noel Grandin wrote: My "make check" is pausing for console input when I use "export DEBUGCPPUNIT=TRUE" Not exactly conducive to easy testing :-) Oh - perhaps you have to type 'run' to run the unit tests ? :-)

Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Michael Meeks
On Tue, 2012-07-10 at 13:08 +0200, Noel Grandin wrote: > My "make check" is pausing for console input when I use "export > DEBUGCPPUNIT=TRUE" > Not exactly conducive to easy testing :-) Oh - perhaps you have to type 'run' to run the unit tests ? :-) I assume you'd not want to do a 'make

make check with DEBUGCCPUNIT=TRUE is waiting for console output

2012-07-10 Thread Noel Grandin
Hi My "make check" is pausing for console input when I use "export DEBUGCPPUNIT=TRUE" Not exactly conducive to easy testing :-) This is on an Ubuntu 12.04 linux system. Any ideas on how to debug this? Thanks, Noel Grandin Disclaimer: http://www.peralex.com/disclaimer.html