On 22/05/15 04:31, Ryota Ozaki wrote:
Inspired by that, I'm adding this code in the cleanup phase:
if [ -f rump_server.core ]; then
gdb -batch -ex bt /usr/bin/rump_server rump_server.core
fi
It's helpful :)
good ;)
Btw, why the absolute paths? I meant to ask about it in your test
example from yesterday, but forgot. I think it's perfectly reasonable
to be able to set PATH/LD_LIBRARY_PATH and run the test suite on some
development code without having to resort to chroots or something like that.
Now, understandably, defining such testing abstractions may not be what you
want to spend time on now, though I think it would quickly start saving a
lot of time, especially if you want to introduce the log capability to a
large number of tests. So, if you or nobody else has any ideas on what the
higher level construct should be, I can add support for -L. ... anyone?
My opinion at this point is that something like -L option is needed anyway,
but of course more smart solution is welcome if exist.
The problem is that if -L is introduced, we have to keep supporting it.
What about semantics, then? A single -L which completely replaces
standard output is the easiest to implement (only need to touch
rump_server), but is it enough? Or should additional -L options
preserve previous output?
