|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
[boost][test] how to define path to errorThis is an output of failed test: -*- mode: compilation; default-directory: "d:/trash/libraries/" -*- Compilation started at Thu Jun 18 17:21:09 bjam test/ toolset=msvc
...patience... ...found 1286 targets... ...updating 2 targets... testing.capture-output bin\test\Function.test\msvc-8.0\debug\link-static\threading-multi\Function.run ====== BEGIN OUTPUT ======
Running 1 test case... Function.cpp(26): fatal error in "FunctionConstruction": critical check pf->Name() == "F13" failed [F1 != F13] *** 1 failure detected in test suite "foo_test"
Detected memory leaks! Dumping objects -> {235} normal block at 0x003A7C88, 32 bytes long. Data: < T1 > 00 00 00 00 CD CD CD CD 54 31 00 CD CD CD CD CD {234} normal block at 0x003A7E00, 96 bytes long.
Data: < T1 > 00 00 00 00 CD CD CD CD 54 31 00 CD CD CD CD CD {233} normal block at 0x003A7D88, 76 bytes long. Data: < E ~: > F4 D9 45 00 00 00 00 00 CD CD CD CD 00 7E 3A 00
Object dump complete. EXIT STATUS: 201 ====== END OUTPUT ====== emacs compile buffer doesn't recognize the error. I decide to customize an error parser. The advice how to do it (http://stackoverflow.com/questions/1011364/teach-emacs-recognize-boost-test-errors).
My question is how to get full path to Function.cpp. In example above it is d:/trash/libraries/test/Function.cpp. The bjam was started from d:/trash/libraries/ -- Regards, Andrey _______________________________________________ Boost-Testing mailing list Boost-Testing@... http://lists.boost.org/mailman/listinfo.cgi/boost-testing |
|
|
Re: [boost][test] how to define path to errorAMDG
Andrey Torba wrote: > This is an output of failed test: > > -*- mode: compilation; default-directory: "d:/trash/libraries/" -*- > Compilation started at Thu Jun 18 17:21:09 > > bjam test/ toolset=msvc > ...patience... > ...found 1286 targets... > ...updating 2 targets... > testing.capture-output > bin\test\Function.test\msvc-8.0\debug\link-static\threading-multi\Function.run > ====== BEGIN OUTPUT ====== > Running 1 test case... > Function.cpp(26): fatal error in "FunctionConstruction": critical check > pf->Name() == "F13" failed [F1 != F13] > > *** 1 failure detected in test suite "foo_test" > Detected memory leaks! > Dumping objects -> > {235} normal block at 0x003A7C88, 32 bytes long. > Data: < T1 > 00 00 00 00 CD CD CD CD 54 31 00 CD CD CD CD CD > {234} normal block at 0x003A7E00, 96 bytes long. > Data: < T1 > 00 00 00 00 CD CD CD CD 54 31 00 CD CD CD CD CD > {233} normal block at 0x003A7D88, 76 bytes long. > Data: < E ~: > F4 D9 45 00 00 00 00 00 CD CD CD CD 00 7E 3A 00 > Object dump complete. > > EXIT STATUS: 201 > ====== END OUTPUT ====== > > emacs compile buffer doesn't recognize the error. I decide to customize an > error parser. The advice how to do it ( > http://stackoverflow.com/questions/1011364/teach-emacs-recognize-boost-test-errors > ). > My question is how to get full path to Function.cpp. > In example above it is d:/trash/libraries/test/Function.cpp. The bjam was > started from d:/trash/libraries/ > This list is really for the Boost regression tests, not for Boost.Test. Try posting to the users lists. In Christ, Steven Watanabe _______________________________________________ Boost-Testing mailing list Boost-Testing@... http://lists.boost.org/mailman/listinfo.cgi/boost-testing |
|
|
Re: [boost][test] how to define path to errorAndrey Torba <andreytorba <at> gmail.com> writes:
> My question is how to get full path to Function.cpp. > In example above it is d:/trash/libraries/test/Function.cpp. The bjam Bot much I can do here. Boost.Test relies on the value of the macro __FILE__ (I do not strip it - you get what I have). I believe it depends on how you compile it. In some cases it produces full path. Maybe Boost.Build guys can pitch in. Gennadiy _______________________________________________ Boost-Testing mailing list Boost-Testing@... http://lists.boost.org/mailman/listinfo.cgi/boost-testing |
|
|
Re: [boost][test] how to define path to errorAMDG
Gennadiy Rozental wrote: > Andrey Torba <andreytorba <at> gmail.com> writes: > >> My question is how to get full path to Function.cpp. >> In example above it is d:/trash/libraries/test/Function.cpp. The bjam >> > > Bot much I can do here. Boost.Test relies on the value of the macro __FILE__ (I > do not strip it - you get what I have). I believe it depends on how you compile > it. In some cases it produces full path. Maybe Boost.Build guys can pitch in. > The relevant compiler option is /FC which causes the compiler to use full paths. In Christ, Steven Watanabe _______________________________________________ Boost-Testing mailing list Boost-Testing@... http://lists.boost.org/mailman/listinfo.cgi/boost-testing |
| Free embeddable forum powered by Nabble | Forum Help |