I did not need to do anything quite so clumsy with the command line this time.
I was using a find to deliver files to cccc
find . -regex '.*.\(h\|c\|cxx\|cpp\)$' | cccc
--outdir=/home/thomasthorne/cccc_ouput/ -
Seems a resolvable enough use case to me. If I feed only the last file that
was being parsed into the program it completes. My find seems to put out 489
items, which does not sound very large.
$ cloc .
551 text files.
551 unique files.
17 files ignored.
http://cloc.sourceforge.net v 1.60 T=1.38 s (388.1 files/s, 188981.2 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
C++ 146 10694 16757 62416
C 77 19894 28463 59307
C/C++ Header 257 9316 19746 25332
HTML 50 1166 1072 5705
XML 2 0 2 115
make 1 10 13 13
DOS Batch 1 2 1 6
-------------------------------------------------------------------------------
SUM: 534 41082 66054 152894
-------------------------------------------------------------------------------
I would have expected the tool to be able to handle more than 150k lines
of code. I guess there must be something in my code base it does not
like.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504454
Title:
cccc crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cccc/+bug/1504454/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
