No syserr, no syslog. Core down after using special_item_group item...

[-TÜRK- 23]

Hello guys. This problem took my two days and still alive...

 

I have this arguments in my special_item_group.txt (from offi content) All of this items are exists in database.

Group	eva_box			
{				
	Vnum	50124		
	1	71114	5	40
	2	71116	5	30
	3	71118	5	20
	4	71120	5	10
}				
				

When I click 50124 vnum item core locks & after 5-10 seconds core down. There is no syslog, no syserr. Core make 950MB .core file! So I can't trace .core file..

 

Just tells extracted item name & vnum in syslog.

Feb 18 14:41:56.816539 :: USE_ITEM USED_ITEM_NAME, Inven 0, Cell 65535, ItemType 23, SubType 0
Feb 18 14:41:56.816616 :: LOG: INSERT DELAYED INTO log  (type, time, who, x, y, what, how, hint, ip, vnum) VALUES('ITEM', NOW(), 24, 955647, 249552, 10000002, 'SYSTEM', 'EXTRACTED_ITEM_NAME', '192.168.56.1', 71120)
Feb 18 14:41:56.816635 :: 7: 71120 5

What I made:

 

I changed CORE branches (Novaline & mainline)

I changed DB revisions.

I deleted all quests.

I changed special_item_group arguments.

I added & removed tabs in special_item_group.txt

I changed Item names.

 

....

 

Any ideas     

 

I'm Using FreeBSD-9.1x64

[ATAG 309]

 

Inven 0, Cell 65535

It's very interesting...

[-TÜRK- 23]

It's very interesting...

 

For sure! I did not see that before...

 

Thats normal USE_ITEM prefix:

TestChar01: USE_ITEM Elektromanyetik Pala+3 (inven 1, cell: 1)

[ATAG 309]

The longer message is made by the test_server mode.

Try to set the item flag "ITEM_FLAG_LOG", maybe you will get more details...

[-TÜRK- 23]

The longer message is made by the test_server mode.

Try to set the item flag "ITEM_FLAG_LOG", maybe you will get more details...

 

I can't get any details... 

 

I need solution guys..

[-TÜRK- 23]

Still I have this problem.

 

Core stacktrace don't have any filename just adress:

 

Core was generated by `bin'.

Program terminated with signal 11, Segmentation fault.

#0  0x288d838c in ?? ()

 

(??)