Hi,
First of all thanks.
Now I am able to destroy the octstr *respstr, By pointing it to NULL.

Actually I was storing a delivery report in Octstr *dlrstr(which is
identical to Octstr *respstr) for my customer requirement.
But I am not able to destry that.

Regards
Jyoti Ranjan Panda

-----Original Message-----
From: Nikos Balkanas [mailto:[email protected]]
Sent: Tuesday, March 17, 2009 9:47 PM
To: Werner Coetzee; jyoti; [email protected]
Subject: Re: unable to destroy Octstr *respstr


Hi,

If you want to destroy it anyway (personal reasons) remember to set the pdu
pointer to NULL. But why you want to do this is beyond me.

BR,
Nikos
----- Original Message -----
From: "Werner Coetzee" <[email protected]>
To: "jyoti" <[email protected]>; <[email protected]>
Sent: Tuesday, March 17, 2009 3:03 PM
Subject: RE: unable to destroy Octstr *respstr



Why do you want to destroy it?

It's only a pointer to the short_message or message_payload fields in the
received PDU,
which will be destroyed when the pdu is destroyed.

Regards

--

    Werner Coetzee
*   C Developer: Messaging Engine

*   T +27 21 910 7700
*   F +27 21 910 7701

    [email protected]
    www.clickatell.com




-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of jyoti
Sent: 17 March 2009 15:01
To: [email protected]
Subject: unable to destroy Octstr *respstr

Hi,
I am not able to destroy  Octstr *respstr defined in
/gateway-1.4.3/gw/smsc/smsc.smpp.c/static Msg *handle_dlr function.
As its a Octstr type I should  be able to destroy the memory, but on trying
this I am geting PANIC.

regards
Jyoti Ranjan Panda


--

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E-MAIL.

This e-mail message and all attachments transmitted with it are confidential
and are intended solely for the addressee(s). If the reader of this message
is not the intended recipient, you are hereby notified that any reading,
dissemination, distribution, copying, or other use of this message or its
attachment(s) is strictly prohibited.




Reply via email to