Re: smsd crash report

[Chuck]

Hi,

I have collected several crash dumps and logs.

They all seem to fail sending an sms message, and then receive an unexpected 
sms message.

-------------------
#0  0xb7612c84 in NK6510_IncomingSMS (messagetype=2, message=0x80e89f0 "\001|", 
length=58, data=0x82a7c70, state=0xb5ebe008) at nk6510.c:1928

log:
Sending SMS: +<removed>
Inserting Event: 0
Processing Event: 0
Message sent: 0x02 / 0x0006
00 01 00 14 01 00                               |                 
Message received: 0x02 / 0x000e
01 7c 00 03 00 01 0c 08 01 26 63 00 00 00       |  |       &c     
Received message type 02
Frame of type 0x02 (SMS handling) received!
SMS sending failed
=====> ENTER gn_sms_send()
enc_chars: 47
ext_chars: 0
total: 42
size of the input string: 47 bytes
number of characters in the input string: 47 chars
=====> ENTER sms_send_single()
General Data Coding
Default Alphabet
        size: 42
        offset: 0
        encoded size: 42
        rawsms length: 47
        rawsms user data length: 42
dcs: 0x00
Length: 0x2f
user_data_length: 0x2a
ValidityIndicator: 2
user_data: <removed>
Input is 47 bytes long
SMS is 42 octets long
Sending
Sending SMS...(94)
Message sent: 0x02 / 0x005e
00 01 00 02 00 00 00 55 55 01 02 54 11 00 00 00 |        UU  T    
00 04 82 0c 01 08 0c 91 19 89 81 54 84 88 82 0c |            T    
02 01 00 00 00 00 00 00 00 00 80 30 2a 2f e3 b0 |            0*/  
9b 9c 27 cb cb e1 36 ad 0e 4a cf 41 ee f7 1d f4 |   '   6  J A    
76 b3 d3 ee 32 08 00 ba df ef ae 76 7e 1c 6e cf | v   2      v~ n 
e1 e1 71 d9 35 7e b7 01 55 55 08 04 01 a9       |   q 5~  UU      
Message received: 0x02 / 0x003a
01 7c 00 15 00 01 0b 34 01 e1 00 00 ff 02 82 0c |  |     4        
02 08 07 91 31 21 13 94 18 f0 81 20 1a 00 00 53 |     1!         S
00 4d 00 53 00 20 00 53 00 65 00 74 00 74 00 69 |  M S   S e t t i
00 6e 00 67 00 73 00 00 00 00                   |  n g s          
Received message type 02
Frame of type 0x02 (SMS handling) received!
SMSC Received
SMSC received but not expected
-----------------


second crash type:
-----------------


chuck

On Fri, May 13, 2011 at 09:27:29PM +0200, Pawel Kot wrote:
> Hi,
> 
> On Fri, May 13, 2011 at 21:17, Chuck <address@hidden> wrote:
> > On Wed, May 04, 2011 at 12:26:10PM +0200, Pawel Kot wrote:
> >> On Wed, May 4, 2011 at 01:45, Chuck <address@hidden> wrote:
> >> > I have noticed regular smsd crashes with the version "GNOKII Version 
> >> > 0.6.31git". ?I have several core dumps, each of which has a backtrace 
> >> > that terminates in nk6510.c, line 1921:
> 
> Git from today should not crash, but I guess there might be some
> failures with sending.
> 
> >> > Core was generated by `/usr/local/bin/smsd -u xxxxx -p xxxxx -d xxxxx -c 
> >> > xxxxxxxxx -m mysql -b IN -f /'.
> >>
> >> Thanks for this information. Does it happen on the first incoming
> >> message? Or after you get several ones?
> 
> Sorry, I meant outgoing message not incoming message.
> 
> > The log indicates that several messages were received.
> >
> >>
> >> > Program terminated with signal 11, Segmentation fault.
> >> > [New process 18407]
> >> > [New process 18408]
> >> > [New process 18406]
> >> > #0 ?0xb76bbd42 in NK6510_IncomingSMS (messagetype=2,
> >> > ? ?message=0x80e89f0 "\001|", length=58, data=0x81c6c98, 
> >> > state=0xb60a5008)
> >> > ? ?at nk6510.c:1921
> >> > 1921 ? ? ? ? ? ? ? ? ? ?data->message_center->id = message[8];
> >>
> >> So that's most likely because data->message_center is NULL. We'd need
> >> to find a reason why it is so.
> >>
> >> >
> >> > The phone identifies as a Nokia 6300:
> >> > [38885385.242588] usb 1-2: New USB device found, idVendor=0421, 
> >> > idProduct=04f9
> >> > [38885385.242588] usb 1-2: New USB device strings: Mfr=1, Product=2, 
> >> > SerialNumber=0
> >> > [38885385.242588] usb 1-2: Product: Nokia 6300
> >> > [38885385.242588] usb 1-2: Manufacturer: Nokia
> >> >
> >> > Is there any other information I can provide to aid in tracking down the 
> >> > cause of this crash?
> >>
> >> Based on the information you have provided you're using series40
> >> driver. However it is always useful to get the config, debug log, and
> >> in case of smsd also xdebug log.
> >
> > It appeared that debug and xdebug output both went to stderr, as I ran smsd 
> > via nohup and the expected output appeared in nohup.out.
> 
> Thanks, that's appreciated.
> 
> > The end of nohup.out is as follows:
> > Using GetSMSFolderStatus for Series40 3rd Ed
> > Trying to retrieve filelist of C:\predefmessages\1\*.* from cache
> > Getting key C:\predefmessages\1\*.* from map 0xb5f027f0.
> > Getting key C:\predefmessages\1\*.* from map 0xb5f027f0.
> > 0 out of 4 are SMS
> > GN_OP_GetSMSFolderStatus returned (number) 0
> > phoneMonitor.sms.number 0
> > Sending SMS: XXXXXXXXXXX, text of message
> > Inserting Event: 0
> > Processing Event: 0
> > Message sent: 0x02 / 0x0006
> > 00 01 00 14 01 00 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? |
> > Message received: 0x02 / 0x003a
> > 01 7c 00 15 00 01 0b 34 01 e1 00 00 ff 02 82 0c | ?| ? ? 4
> > 02 08 07 91 31 21 13 94 18 f0 81 20 1a 00 00 53 | ? ? 1! ? ? ? ? S
> > 00 4d 00 53 00 20 00 53 00 65 00 74 00 74 00 69 | ?M S ? S e t t i
> > 00 6e 00 67 00 73 00 00 00 00 ? ? ? ? ? ? ? ? ? | ?n g s
> > Received message type 02
> > Frame of type 0x02 (SMS handling) received!
> > SMSC Received
> > =====> ENTER gn_sms_send()
> 
> OK, that's strange now. Can you please show the full backtrace? It
> does not match the backtrace that you've shown before.
> 
> -- 
> Pawel Kot