RE: Kannel crashes sendsms in emi2 and dlrmask=7
João Miranda <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Stipe,
I made a patch for sdb_callback_add, and the 'Row has wrong length 1' error gone. But I still get 'PANIC: gwlib/list.c:425: lock: Assertion `list != NULL' failed.'.
Can you validate the patch and help me with the Assertion error?
static int sdb_callback_add(int n, char **p, void *row)
{
int i;
Octstr *dlr_row;
if (!n) {
debug("dlr.sdb", 0, "no rows found");
return 0;
}
dlr_row = octstr_create("");
for (i = 0; i < n; i++) {
if (i != 0) {
octstr_append_char(dlr_row, ' ');
}
octstr_append(dlr_row, octstr_imm(p[i]));
}
/* strip string into words */
row = octstr_split(dlr_row, octstr_imm(" "));
if (list_len(row) != 4) {
debug("dlr.sdb", 0, "Row has wrong length %ld", list_len(row));
return 0;
}
octstr_destroy(dlr_row);
return 0;
}
-----Original Message-----
From: Stipe Tolj [mailto:[email protected]]
Sent: Monday, December 02, 2002 10:31
To: João Miranda
Cc: [email protected]
Subject: Re: Kannel crashes sendsms in emi2 and dlrmask=7
João Miranda schrieb:
>
> Hi list,
>
> I'm trying to send messages with drlmask=7 and libsdb configured.
> The kannel crashes after sending the first message. Can anyone help me??
>
> bearerbox log:
> 2002-11-26 11:44:54 [0] INFO: Kannel bearerbox II version 1.2.1 starting
> 2002-11-26 11:44:54 [0] INFO: MAIN: Start-up done, entering mainloop
> 2002-11-26 11:44:54 [0] DEBUG: EMI2[VODAFONE-4447]: start called
> 2002-11-26 11:44:54 [5] INFO: EMI2[VODAFONE-4447]: connecting to Primary SMSC
> 2002-11-26 11:44:54 [6] DEBUG: sms_router: time to sleep
> 2002-11-26 11:44:54 [6] DEBUG: sms_router: list_len = 0
> 2002-11-26 11:44:54 [5] DEBUG: EMI2[VODAFONE-4447]: Sending operation type 60, message with password not shown in log file.
> 2002-11-26 11:44:54 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 parsing packet: <^B00/00019/R/60/A//6D^C>
> 2002-11-26 11:44:54 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 sending packet: <^B00/00026/O/31/4447/0539/C9^C>
> 2002-11-26 11:44:54 [5] DEBUG: EMI2[VODAFONE-4447]: Got packet from the main socket
> 2002-11-26 11:44:54 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 parsing packet: <^B00/00023/R/31/A/0000/26^C>
> 2002-11-26 11:44:59 [4] DEBUG: Started thread 7 (gw/bb_boxc.c:function)
> 2002-11-26 11:44:59 [7] INFO: Client connected from <127.0.0.1>
> 2002-11-26 11:44:59 [7] DEBUG: Started thread 8 (gw/bb_boxc.c:boxc_sender)
> 2002-11-26 11:45:16 [7] DEBUG: boxc_receiver: sms received
> 2002-11-26 11:45:16 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 sending packet: <^B01/00075/O/51/919115275/4447//1//7/////////////3//5465737431/////////////30^C>
> 2002-11-26 11:45:16 [5] DEBUG: EMI2[VODAFONE-4447]: Got packet from the main socket
> 2002-11-26 11:45:16 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 parsing packet: <^B01/00042/R/51/A//919115275:261102114410/02^C>
> 2002-11-26 11:45:20 [5] DEBUG: EMI2[VODAFONE-4447]: Got packet from the main socket
> 2002-11-26 11:45:20 [5] DEBUG: EMI2[VODAFONE-4447]: emi2 parsing packet: <^B00/00287/O/53/1921681390409147/919115275/////////////261102114410/0/000/261102114414/3//41206D656E736167656D207061726120393139313135323735206964656E746966696361646120706F722030323131323631313434313020666F6920656E74726567756520656D2030322D31312D32362061732031313A34343A3134/////////////87^C>
> 2002-11-26 11:45:20 [5] DEBUG: Row has wrong length 1
> 2002-11-26 11:45:20 [5] PANIC: gwlib/list.c:425: lock: Assertion `list != NULL' failed.
whoops. The debug line 'row has wrong length 1' may be the cause.
Checking in the source...
Yep, it's in the sdb_callback_add() routine. You get only *1* row as
result.
Can you please check gw/dlr.c:sdb_callback_add() routine and add some
debugging information there while processing the SMS. This would be
very usefull to figure out what there is going on.
Stipe
[email protected]
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are