If devtodo is run when the TERM env variable is not yet set (for example, if it loads in your .bash_profile before an Xterm loads while loading X or if you want to email the output of your todo list in a cronjob), then devtodo will throw a runtime exception, which in turn calls abort(), which of course will dump core if the core limit is non-zero. Of course, this is an upstream bug, but I've attached a patch until it can be fixed upstream.
Created attachment 37339 [details, diff] devtodo-fix-TERM-sigabrt.patch
Added to portage.