ZBatt segfaults hilariously when there's A/C but no Battery

[amagura]

My laptop can't charge it's own battery, so I have an external (dedicated) charger that I bought a while ago so that I can still enjoy mobility of that my laptop (barely) offers.

So today, after I got back from hooking my battery up to its charger, I was having problems getting my wifi to work, and while trying to debug that I came across the following logs in systemd's journal (note that these are not the original logs):

-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jan 29 22:02:58 Aya kernel: zbatc[2169]: segfault at 0 ip 00007f8023169854 sp 00007fff9343fad0 error 4 in libc-2.20.so[7f8023100000+199000]
Jan 29 22:02:58 Aya kernel: zbatt[2172]: segfault at 0 ip 00007fdf67005854 sp 00007fffc8b76050 error 4 in libc-2.20.so[7fdf66f9c000+199000]
Jan 29 22:03:00 Aya kernel: zbatc[2177]: segfault at 0 ip 00007fbc9a482854 sp 00007fff6e40e1f0 error 4 in libc-2.20.so[7fbc9a419000+199000]
Jan 29 22:03:00 Aya kernel: zbatt[2180]: segfault at 0 ip 00007f91601c7854 sp 00007fff178783f0 error 4 in libc-2.20.so[7f916015e000+199000]
Jan 29 22:03:00 Aya systemd-coredump[2178]: Process 2177 (zbatc) of user 1000 dumped core.
-- Subject: Process 2177 (zbatc) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 2177 (zbatc) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jan 29 22:03:00 Aya systemd-coredump[2181]: Process 2180 (zbatt) of user 1000 dumped core.
-- Subject: Process 2180 (zbatt) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 2180 (zbatt) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

Note that the above core dumps occur every time Zsh redisplays the prompt.

What I'd like to do is setup some cool error patterns using the output of zbatt and zbatc to indicate which error is currently occuring, so that users won't have to get annoyed with error messages popping up every time their prompt redisplays while still allowing them to know that an error has occurred.