Re: SIGSEGV a bug or a feature?

On 2004-02-03, Joel Garry <joel-garry_at_home.com> wrote:

>> 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?
>
> Send the data to metalink and crash _their_ server!

I don't have sqlnet access to their database server ;)

> Which process are you referring to? If it is just a spawned beq they
> might have a point, user written application bugs are out of their
> purview.

Yes, but really - should I be able to send data to a spawned session and force it to die with a segmentation violation. Shouldn't I get a more meaningful explanation than EOF on communication channel? I can't help but wonder how many more input validation errors there are in Oracle.

> The database should just rollback and go on.

And it does (after dumping an appropriate trace file of course)

-- 
Andreas Plesner Jacobsen | NANCY!!  Why is everything RED?!