Re: unable to destroy Octstr *respstr

2009-03-18 Thread Nikos Balkanas

Hi,

Why not? Same deal. After destroying it set its parent pointer to NULL. 
octstr_destroy checks before freeing a NULL pointer. Of course you realize 
that by intervening like that you are branching off cvs, and any subsequent 
updates to the affected files will have to be merged.


BR,
Nikos

- Original Message - 
From: jyoti jyoti.ran...@cellnext.com
To: Nikos Balkanas nbalka...@gmail.com; Werner Coetzee 
werner.coet...@clickatell.com; devel@kannel.org; 
:afink@list.fink.org

Sent: Wednesday, March 18, 2009 7:13 AM
Subject: RE: unable to destroy Octstr *respstr




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:nbalka...@gmail.com]
Sent: Tuesday, March 17, 2009 9:47 PM
To: Werner Coetzee; jyoti; devel@kannel.org
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 werner.coet...@clickatell.com
To: jyoti jyoti.ran...@cellnext.com; devel@kannel.org
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

   werner.coet...@clickatell.com
   www.clickatell.com




-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf
Of jyoti
Sent: 17 March 2009 15:01
To: devel@kannel.org
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.








Re: unable to destroy Octstr *respstr

2009-03-17 Thread Donald Jackson
Can you provide the log of the PANIC?

My guess is you are trying to destroy a previously destroyed or
uninitialized Octstr *. But that's a wild guess :)

2009/3/17 jyoti jyoti.ran...@cellnext.com

 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





-- 
Donald Jackson
http://www.ddj.co.za/
donaldjster(a)gmail.com


RE: unable to destroy Octstr *respstr

2009-03-17 Thread Werner Coetzee

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

werner.coet...@clickatell.com
www.clickatell.com




-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf Of 
jyoti
Sent: 17 March 2009 15:01
To: devel@kannel.org
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.




Re: unable to destroy Octstr *respstr

2009-03-17 Thread Nikos Balkanas

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 werner.coet...@clickatell.com

To: jyoti jyoti.ran...@cellnext.com; devel@kannel.org
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

   werner.coet...@clickatell.com
   www.clickatell.com




-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf 
Of jyoti

Sent: 17 March 2009 15:01
To: devel@kannel.org
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.






RE: unable to destroy Octstr *respstr

2009-03-17 Thread jyoti

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:nbalka...@gmail.com]
Sent: Tuesday, March 17, 2009 9:47 PM
To: Werner Coetzee; jyoti; devel@kannel.org
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 werner.coet...@clickatell.com
To: jyoti jyoti.ran...@cellnext.com; devel@kannel.org
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

werner.coet...@clickatell.com
www.clickatell.com




-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf
Of jyoti
Sent: 17 March 2009 15:01
To: devel@kannel.org
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.