Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running cath-ssaps on files in other directories can causes errors #35

Open
tonyelewis opened this issue Jun 23, 2017 · 2 comments
Open
Assignees

Comments

@tonyelewis
Copy link
Contributor

Eg cath-ssap ../1c0pA01 ../1hdoA00 gives:

Cannot open file "./../1c0pA01../1hdoA00.list" for writing [ios_base::clear: unspecified iostream_category error] : No such file or directory
Whilst running program /cath-tools/ninja_clang_relwithdebinfo/cath-ssap (via a program_exception_wrapper with typeid: "N4cath30ssap_program_exception_wrapperE"), caught a boost::exception:
../source/common/file/open_fstream.hpp(72): Throw in function void cath::common::detail::open_fstream_impl(fstream_t &, const boost::filesystem::path &, const std::ios_base::openmode &, const cath::common::detail::fstream_type &) [fstream_t = std::__1::basic_ofstream<char, std::__1::char_traits<char> >]
Dynamic exception type: boost::exception_detail::clone_impl<cath::common::runtime_error_exception>
std::exception::what: Cannot open file "./../1c0pA01../1hdoA00.list" for writing [ios_base::clear: unspecified iostream_category error] 
@tonyelewis tonyelewis self-assigned this Jun 23, 2017
@tonyelewis
Copy link
Contributor Author

Implementation note:

@tonyelewis
Copy link
Contributor Author

I've made some effort towards improving the handling of names in 9831df9.

This leaves me clearer that the original cath-ssap command is in error because the positional arguments are being treated as IDs. Instead, the same could be achieved with:

cath-ssap --pdb-path .. 1c0pA01 1hdoA00

That said, cath-ssap should:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant