"adb kill" - does it need a root'ed device?

[Espen Riskedal]

On my S2 I've got at the moment several stale gdbservers still running:

  app_120   17532 1     476    200   ffffffff 00000000 S
/data/data/eu.licentia.necessitas.industrius.example.fontdrawtest/lib/gdbserver
  app_120   17584 1     476    200   ffffffff 00000000 S
/data/data/eu.licentia.necessitas.industrius.example.fontdrawtest/lib/gdbserver

killing them doesn't work it seems:

  espen at droid:~/dev/android-sdk-linux_x86/platform-tools$ sudo ./adb
shell kill 17532
  could not kill pid 17532: Operation not permitted
  espen at droid:~/dev/android-sdk-linux_x86/platform-tools$ sudo ./adb
shell kill -9 17532
  could not kill pid 17532: Operation not permitted
  espen at droid:~/dev/android-sdk-linux_x86/platform-tools$ sudo ./adb
shell kill -10 17532
  could not kill pid 17532: Operation not permitted

The device is not root'ed/hacked (if there is such a thing for
Android) - anyone else got tips for this?

espen