2005-02-15 19:29:49 [31332] [0] WARNING: WTP: got a truncated datagram, ignoring
2005-02-15 19:29:49 [31332] [0] PANIC: wap/wap_events.c:218: wap_event_assert: Assertion `event != NULL' failed.
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_event_assert+0x40) [0x808c19c]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wtp_unpack_wdp_datagram+0x1f0) [0x80a4674]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_dispatch_datagram+0xa4) [0x8081fb8]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(main+0x481) [0x8056480]
2005-02-15 19:29:49 [31332] [0] PANIC: /lib/libc.so.6(__libc_start_main+0xc0) [0x402de460]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox [0x8054611]
ok, the first WARNING would also have more information in debug log-level mode, since the wap_event_dump() is called and we get more information on what is actually inside the datagram. This information is not available in the log, because of the higher log-level.
ok, this is obviously a bug! since we return NULL for unpack_wdp_datagram_real() and directly afterwards do wap_event_assert() and the first gw_assert(event != NULL) brings us to PANIC.
I will file this to Mantis and check for a fix.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
