RE: PANIC: gwlib/octstr.c ...
"Igor Ivoilov" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Certainly! The same error. octstr_imm() is sutable only for static strings. Stipe are you going to change it? How often octstr_case_search is used in such circumstances? Does it worth to create octstr_case_search(Octstr*,char*) ? > -----Original Message----- > From: Stipe Tolj [mailto:[email protected]] > Sent: Tuesday, November 11, 2003 2:45 PM > To: Alexander Malysh > Cc: Igor Ivoilov; [email protected] > Subject: Re: PANIC: gwlib/octstr.c ... > > > Alexander Malysh wrote: > > > > Hi Igor, > > > > ++1 for this patch... > > It's 100% wrong to use octstr_imm for non const c-strings. > And this can also > > explain why we have seen panics with "too many immutable octstr"... > > so, is there any need in changing code at different other places? > > ie. gw/wap_push_pap_mime.c:drop_optional_header() > > Stipe > > mailto:[email protected] > ------------------------------------------------------------------- > Wapme Systems AG > > Münsterstr. 248 > 40470 Düsseldorf, NRW, Germany > > phone: +49.211.74845.0 > fax: +49.211.74845.299 > > mailto:[email protected] > http://www.wapme-systems.de/ > ------------------------------------------------------------------- > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.2.2 (Cygwin) > > mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS > OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 > nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT > dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv > bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID > AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl > OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ > K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H > g2HyLAEKQIp30Q== > =aYCI > -----END PGP PUBLIC KEY BLOCK----- >