SIGSEGV a bug or a feature?

I've recently bumped into an Oracle problem: Due to a problem in DBD::Oracle (at least reproducible when using the latest DBI and DBD::Oracle with 8.1.7.4 libs, but that's not really relevant here), I'm able to crash the Oracle process I am connected to on a 9r2 server. The Oracle process crashes due to a null pointer deref, so this is probably not exploitable for anything other than filling up $ORACLE_HOME with trace files.

My only problem is: Oracle won't acknowledge that this is a bug. The claim is: This is an application sending us bad data, so we don't see a problem in handling this with a server-side crash (which gives the client a nice EOF on communications channel, but no good error message).

So, what's your take on this? Isn't this a bug in Oracle? Should ANY invalid data be able to crash the Oracle process it's connected to?

-- 
Andreas Plesner Jacobsen | Change your thoughts and you change your world.