gearmand crash on GEARMAN_COMMAND_WORK_EXCEPTION

[Brandon Checketts]

Problem: gearmand sometimes crashes when worker sends GEARMAN_COMMAND_WORK_EXCEPTION

Gearmand version 1.0.3

Command line arguments:
usr/local/sbin/gearmand --pid-file=/var/run/gearman/gearmand.pid --user=gearman --backlog=32 --job-retries=0 --port=4730 --listen=10.0.0.10 --threads=0 --file-descriptors=1024 --worker-wakeup=0 --round-robin -q libsqlite3 --libsqlite3-db=/tmp/gearman.sqlite3 --verbose DEBUG

More complete log output available at http://pastebin.com/qGZHkzD2

  DEBUG 2013-04-03 03:07:10.164516 [ main ] 10.0.0.10:55566 Ready POLLIN -> libgearman-server/gearmand_con.cc:118
  DEBUG 2013-04-03 03:07:10.164529 [ main ] read 72 bytes -> libgearman-server/io.cc:696
   INFO 2013-04-03 03:07:10.164535 [ main ] Gear unpack
  DEBUG 2013-04-03 03:07:10.164540 [ main ] GEAR length: 25 gearmand_command_t: GEARMAN_COMMAND_WORK_EXCEPTION -> libgearman-server/plugins/protocol/gear/protocol.cc:248
  DEBUG 2013-04-03 03:07:10.164546 [ main ] Received WORK_EXCEPTION 10.0.0.10:9780089 -> libgearman-server/thread.cc:318
  DEBUG 2013-04-03 03:07:10.164551 [ main ] 10.0.0.10:55566 packet command WORK_EXCEPTION -> libgearman-server/server.cc:98

Begin stack trace, frames found: 11
?0 0x4180f3 in /usr/local/sbin/gearmand() [0x4180f3]
?1 0x4094a5 in /usr/local/sbin/gearmand() [0x4094a5]
?2 0x7f3066c39cb0 in /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f3066c39cb0]
?3 0x421fb8 in /usr/local/sbin/gearmand() [0x421fb8]
?4 0x423aad in /usr/local/sbin/gearmand() [0x423aad]
?5 0x41d509 in /usr/local/sbin/gearmand() [0x41d509]
#6 0x7f30679dd94c in event_base_loop at /usr/lib/libevent-2.0.so.5
?7 0x41a900 in /usr/local/sbin/gearmand() [0x41a900]
?8 0x408c5c in /usr/local/sbin/gearmand() [0x408c5c]
#9 0x7f306688c76d in __libc_start_main at /lib/x86_64-linux-gnu/libc.so.6
?10 0x40926d in /usr/local/sbin/gearmand() [0x40926d]

Clients are using pecl gearman version 1.1.0 linked to gearman-0.27 libraries, so there may be some incompatibilities there (but still, the gearmand process still shouldn't crash)

This may be a duplicate of #1043324, but that doesn't seem to be related to the gearmand server