Postgres Pro
Downloads
Home   >   mailing lists

Re: NULL dereference when memory is tight - Mailing list psycopg

From Daniele Varrazzo
Subject Re: NULL dereference when memory is tight
Date
Msg-id AANLkTinMQwZDCpGCZcbHE7exyNsp18UQ9SLDq0K8Jwq2@mail.gmail.com
Whole thread Raw
In response to NULL dereference when memory is tight  (Brian Sutherland <brian@vanguardistas.net>)
Responses Re: NULL dereference when memory is tight
List psycopg
Tree view 
On Sun, Feb 20, 2011 at 4:47 PM, Brian Sutherland
<brian@vanguardistas.net> wrote:
> Hi,
>
> I recently found a few places in the latest beta release where a NULL
> dereference could occur when insufficient memory is available.
>
> For example in connection_type.c:
>
>     830     self->dsn = strdup(dsn);
>     ...
>     855     pos = strstr(self->dsn, "password");
>
> strdup could return a NULL.
>
> Admittedly this is probably a minor bug, but would it interest anyone if
> I report these somewhere?

Thank you for the review. Having patches would be even better, but I
will take care of this one.

Cheers

-- Daniele

psycopg by date:

Previous
From: Brian Sutherland
Date:
Subject: NULL dereference when memory is tight
Next
From: Jan Urbański
Date:
Subject: register_hstore does DB queries, does not play well with async connections