This is a false positive in sudo. What's happening is that sudo is taking an error from the program it executed and propagating out to the calling shell. Thus when a called application aborts (i.e. SIGABRT), it also triggers an abort for sudo.
To demonstrate:
$ sudo sh -c 'echo $$'
results in the following in /var/crash:
$ ls -l /var/crash/
total 164
-rw-r----- 1 root whoopsie 29122 May 30 15:32 _bin_dash.0.crash
-rw-r----- 1 root whoopsie 133096 May 30 15:32 _usr_bin_sudo.0.crash
This is a false positive in sudo. What's happening is that sudo is taking an error from the program it executed and propagating out to the calling shell. Thus when a called application aborts (i.e. SIGABRT), it also triggers an abort for sudo.
To demonstrate:
$ sudo sh -c 'echo $$'
results in the following in /var/crash:
$ ls -l /var/crash/ sudo.0. crash
total 164
-rw-r----- 1 root whoopsie 29122 May 30 15:32 _bin_dash.0.crash
-rw-r----- 1 root whoopsie 133096 May 30 15:32 _usr_bin_