According to the Interbase API Guide for Version 6, when using
isc_expand_dpb() you will need to clear the additional memory allocated to
the database parameter buffer by using isc_free(). Funny thing about
isc_free(), I could find any more information in the API guide on what
parameters to pass into it. I am currently avoiding both isc_expand_dpb()
and
isc_free() due to a lack of information on isc_free().

Any guidance on isc_free() is more than welcome because I can see some
obvious uses for isc_expand_dpb().

Thanks in advance.

Tony Mays

-----Original Message-----
From: C R Zamana [mailto:zamana@...]
Sent: Wednesday, March 13, 2002 12:27 PM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Questions about Firebird's API

On Wed, 2002-03-13 at 17:05, Ann W. Harrison wrote:
> At 04:50 PM 3/13/2002 -0300, C R Zamana wrote:
>
>
> > That's ok about commit or rollback. What I'm asking
> >is about the "call sequence" regards to the functions
> >isc_dsql_free_statment() and isc_commit_transaction(),
> >for example. Which is the correct sequence?
> >
> > I'm asking because I'm in trouble with memory
> >leaking problems. Anyway, after some tests, it seems that
> >the problem is in the "prepare" section of my process, e.g.,
> >when I need to allocate the XSQLDA structure.
>
> Where are you seeing a memory leak, in your client app,
> in the gds32 client library, or in the server?
>

In my app. It's a client/server app. The "server" receives
the client's requests, send them to the database using api's
functions, and them replies to the "client". The memory leaking
is in the "server" side.

One of the "memory leaking" problems was solved when
I stopped to use the isc_expand_dpb() function ( thanks! ).
But I think that there are problems yet with some functions.
The "describe" process ( not the "prepare" that I mentioned
above, sorry ), when I need to allocate memory for the
osqlda->sqlvar->sqldata variable. It seems that the memory
allocated in this step is never recovered again.

So, this leads to my other questions in the first
message: how is the correct way to deallocate the memory of
the osqlda structure.

Any help will be welcome.

Thanks.
Best regards.



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/