gnokii-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: smsd crash report


From: Pawel Kot
Subject: Re: smsd crash report
Date: Fri, 13 May 2011 21:27:29 +0200

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]