[Qgis-developer] [solved] qgis 2.2 crash
G. Allegri
giohappy at gmail.com
Fri Mar 7 08:26:47 PST 2014
That's a really bad story. I don' excpet to have complete back
compatibility, but a crash shouldn't happen :(
giovanni
2014-03-07 17:13 GMT+01:00 Enzo Cocca <enzo.ccc at gmail.com>:
> The problem of crash was the simbology of qgis 1.8 that I have used to
> qgis 2.2.
>
> thanks!
>
>
> 2014-03-06 17:04 GMT+01:00 Enzo Cocca <enzo.ccc at gmail.com>:
>
>> hi all,
>>
>> I have one problem with pyarchinit plugin and qgis 2.2 on win7. when I
>> try to make one action with this plugin qgis go in crash. I have an error
>> that win transform in a dump file.
>> I have debugged this file with wdk and below I put the debugging:
>>
>> Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
>> Copyright (c) Microsoft Corporation. All rights reserved.
>>
>>
>> Loading Dump File
>> [C:\Users\user\AppData\Local\Temp\qgis-20140306-094727-5224-6084-c3a2817.dmp]
>> User Mini Dump File: Only registers, stack and portions of memory are
>> available
>>
>> Symbol search path is: *** Invalid ***
>>
>> ****************************************************************************
>> * Symbol loading may be unreliable without a symbol search path.
>> *
>> * Use .symfix to have the debugger choose a symbol path.
>> *
>> * After setting your symbol path, use .reload to refresh symbol
>> locations. *
>>
>> ****************************************************************************
>> Executable search path is:
>> Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
>> Product: WinNt, suite: SingleUserTS
>> Machine Name:
>> Debug session time: Thu Mar 6 09:47:28.000 2014 (UTC + 1:00)
>> System Uptime: not available
>> Process Uptime: 0 days 0:00:36.000
>> ................................................................
>> ................................................................
>> ................................................................
>> ................................................................
>> ........
>> This dump file has an exception of interest stored in it.
>> The stored exception information can be accessed via .ecxr.
>> (1468.17c4): Access violation - code c0000005 (first/second chance not
>> available)
>> *** WARNING: Unable to verify timestamp for ntdll.dll
>> *** ERROR: Module load completed but symbols could not be loaded for
>> ntdll.dll
>> *** WARNING: Unable to verify timestamp for kernel32.dll
>> *** ERROR: Module load completed but symbols could not be loaded for
>> kernel32.dll
>> eax=00000000 ebx=0d980d78 ecx=0ee7a1d0 edx=00000265 esi=0d980d38
>> edi=0043b8cc
>> eip=77c30c32 esp=0043b58c ebp=0043b59c iopl=0 nv up ei pl zr na
>> pe nc
>> cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b
>> efl=00000246
>> ntdll+0x20c32:
>> 77c30c32 83c404 add esp,4
>> 0:000> The stored exception information can be accessed via .ecxr.
>> ^ No runnable debuggees error in 'The stored exception information
>> can be accessed via .ecxr.'
>> 0:000> (1468.17c4): Access violation - code c0000005 (first/second chance
>> not available)
>> ^ Syntax error in '(1468.17c4): Access violation - code c0000005
>> (first/second chance not available)'
>> 0:000> !analayze -v
>> No export analayze found
>> 0:000> !analyze -v
>>
>> *******************************************************************************
>> *
>> *
>> * Exception Analysis
>> *
>> *
>> *
>>
>> *******************************************************************************
>>
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for spatialiteprovider.dll -
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for core.pyd -
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for qgis_gui.dll -
>> ***** OS symbols are WRONG. Please fix symbols to do analysis.
>>
>> ***** OS (WOW64 kernel32) symbols are WRONG. Please fix symbols to do
>> analysis.
>>
>> *************************************************************************
>> *** ***
>> *** ***
>> *** Your debugger is not using the correct symbols ***
>> *** ***
>> *** In order for this command to work properly, your symbol path ***
>> *** must point to .pdb files that have full type information. ***
>> *** ***
>> *** Certain .pdb files (such as the public OS symbols) do not ***
>> *** contain the required information. Contact the group that ***
>> *** provided you with these symbols if you need this command to ***
>> *** work. ***
>> *** ***
>> *** Type referenced: nt!IMAGE_NT_HEADERS32 ***
>> *** ***
>> *************************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> *********************************************************************
>> * Symbols can not be loaded because symbol path is not initialized. *
>> * *
>> * The Symbol Path can be set by: *
>> * using the _NT_SYMBOL_PATH environment variable. *
>> * using the -y <symbol_path> argument when starting the debugger. *
>> * using .sympath and .sympath+ *
>> *********************************************************************
>> Unable to load image C:\Windows\SysWOW64\KERNELBASE.dll, Win32 error 0n2
>> *** WARNING: Unable to verify timestamp for KERNELBASE.dll
>> *** ERROR: Module load completed but symbols could not be loaded for
>> KERNELBASE.dll
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for ole32.dll -
>> *** ERROR: Symbol file could not be found. Defaulted to export symbols
>> for user32.dll -
>> *** WARNING: Unable to verify timestamp for winmm.dll
>> *** ERROR: Module load completed but symbols could not be loaded for
>> winmm.dll
>>
>> FAULTING_IP:
>> QtCore4!QString::operator==+8
>> 67053478 8b4a08 mov ecx,dword ptr [edx+8]
>>
>> EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
>> ExceptionAddress: 67053478 (QtCore4!QString::operator==+0x00000008)
>> ExceptionCode: c0000005 (Access violation)
>> ExceptionFlags: 00000000
>> NumberParameters: 2
>> Parameter[0]: 00000000
>> Parameter[1]: 0000026d
>> Attempt to read from address 0000026d
>>
>> DEFAULT_BUCKET_ID: WRONG_SYMBOLS
>>
>> PROCESS_NAME: qgis-bin.exe
>>
>> ADDITIONAL_DEBUG_TEXT:
>> You can run '.symfix; .reload' to try to fix the symbol path and load
>> symbols.
>>
>> FAULTING_MODULE: 773c0000 kernel32
>>
>> DEBUG_FLR_IMAGE_TIMESTAMP: 53052dad
>>
>> MODULE_NAME: QtCore4
>>
>> ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto
>> riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
>>
>> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto
>> riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
>>
>> EXCEPTION_PARAMETER1: 00000000
>>
>> EXCEPTION_PARAMETER2: 0000026d
>>
>> READ_ADDRESS: 0000026d
>>
>> FOLLOWUP_IP:
>> QtCore4!QString::operator==+8
>> 67053478 8b4a08 mov ecx,dword ptr [edx+8]
>>
>> APP: qgis-bin.exe
>>
>> PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
>>
>> BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
>>
>> LAST_CONTROL_TRANSFER: from 6257b1dd to 67053478
>>
>> STACK_TEXT:
>> WARNING: Stack unwind information not available. Following frames may be
>> wrong.
>> 0043c688 6257b1dd 0043c968 972e5cba 4052e5cb
>> QtCore4!QString::operator==+0x8
>> 0043c784 6252ceeb 0043c968 972e5cba 4052e5cb
>> qgis_core!QgsSvgCache::svgAsImage+0x6d
>> 0043c91c 6252d841 0e8d0358 0043c968 00000000
>> qgis_core!QgsSVGFillSymbolLayer::applyPattern+0x11b
>> 0043c9b4 6253ddcc 00000001 0000ffff 00000000
>> qgis_core!QgsSVGFillSymbolLayer::applyDataDefinedSettings+0x4f1
>> 0043c9e8 6252fc3d 0043caa4 9bbf786d 00000000
>> qgis_core!QgsFeatureRendererV2::_getPolygon+0x36c
>> 0043ca80 624ffd70 0043cafc 00000000 0043caa4
>> qgis_core!QgsImageFillSymbolLayer::renderPolygon+0x6d
>> 0043cac0 6253e593 0043cafc 00000000 05964f08
>> qgis_core!QgsFillSymbolV2::renderPolygon+0xa0
>> 0043cb04 5d30a9f6 0043cb14 0043cb74 6276ec24
>> qgis_core!QgsFeatureRendererV2::renderFeatureWithSymbol+0x383
>> 0043cb18 6255998d 6721175c 00000001 053948e0
>> spatialiteprovider!selectWidget+0x6586
>> 0043cb7c 6269e3d9 053948e0 9bbf7d91 053948e0
>> qgis_core!QgsRuleBasedRendererV2::stopRender+0x10d
>> 0043cc04 626aa880 0043ce04 053948e0 67055a00
>> qgis_core!QgsVectorLayer::drawRendererV2+0x289
>> 0043cdfc 67055a00 0ec829a0 0c622068 0e8e60a0
>> qgis_core!QgsVectorLayer::draw+0x7b0
>> 0043ce10 5cdd6f0b 3f800001 00000000 0043d018
>> QtCore4!QString::localeAwareCompare+0x250
>> 0043ce20 5cdd6f1f 053948e0 0043d03c 0e8e60a0
>> core!OGREnvelope3D::Intersect+0x15f13b
>> 0043d018 607bfbaa 0043d03c 00000000 9bbf61ae
>> core!OGREnvelope3D::Intersect+0x15f14f
>> 0043d06c 6081e600 05329f70 0043d0ec 60888574
>> qgis_gui!QgsMapCanvasMap::render+0x10a
>> 0043d080 607bb610 9bbf610e 0043d710 05329f70
>> qgis_gui!QgsMapCanvas::renderStarting+0x10
>> 0043d0f4 607bf11c 9bbf6082 0043d710 05329f70
>> qgis_gui!QgsMapCanvas::refresh+0x1e0
>> 00000000 00000000 00000000 00000000 00000000
>> qgis_gui!QgsMapCanvas::wheelEvent+0x17c
>>
>>
>> STACK_COMMAND: ~0s; .ecxr ; kb
>>
>> SYMBOL_STACK_INDEX: 0
>>
>> SYMBOL_NAME: qtcore4!QString::operator==+8
>>
>> FOLLOWUP_NAME: MachineOwner
>>
>> IMAGE_NAME: QtCore4.dll
>>
>> BUCKET_ID: WRONG_SYMBOLS
>>
>> FAILURE_BUCKET_ID: WRONG_SYMBOLS_c0000005_QtCore4.dll!QString::operator==
>>
>> Followup: MachineOwner
>> ---------
>>
>> 0:000> lmvm spatialiteprovider.dll
>> start end module name
>> 0:000> lmvm core.pyd
>> start end module name
>> 0:000> lmvm qgis_gui.dll
>> start end module name
>> 0:000> lmvm qgis_gui
>> start end module name
>> 606d0000 609c6000 qgis_gui (export symbols) qgis_gui.dll
>> Loaded symbol image file: qgis_gui.dll
>> Mapped memory image file: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\bin\qgis_gui.dll
>> Image path: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\bin\qgis_gui.dll
>> Image name: qgis_gui.dll
>> Timestamp: Wed Feb 26 14:58:08 2014 (530DF2F0)
>> CheckSum: 00300642
>> ImageSize: 002F6000
>> File version: 0.0.0.0
>> Product version: 0.0.0.0
>> File flags: 0 (Mask 0)
>> File OS: 0 Unknown Base
>> File type: 0.0 Unknown
>> File date: 00000000.00000000
>> Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
>> 0:000> lmvm core
>> start end module name
>> 5cc20000 5d0d1000 core (export symbols) core.pyd
>> Loaded symbol image file: core.pyd
>> Mapped memory image file: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\python\qgis\core.pyd
>> Image path: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\python\qgis\core.pyd
>> Image name: core.pyd
>> Timestamp: Wed Feb 26 14:56:22 2014 (530DF286)
>> CheckSum: 004AC88F
>> ImageSize: 004B1000
>> File version: 0.0.0.0
>> Product version: 0.0.0.0
>> File flags: 0 (Mask 0)
>> File OS: 0 Unknown Base
>> File type: 0.0 Unknown
>> File date: 00000000.00000000
>> Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
>> 0:000> lmvm spatialiteprovider
>> start end module name
>> 5d2f0000 5d335000 spatialiteprovider (export symbols)
>> spatialiteprovider.dll
>> Loaded symbol image file: spatialiteprovider.dll
>> Mapped memory image file: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\plugins\spatialiteprovider.dll
>> Image path: C:\Program Files (x86)\QGIS
>> Valmiera\apps\qgis\plugins\spatialiteprovider.dll
>> Image name: spatialiteprovider.dll
>> Timestamp: Wed Feb 26 14:59:06 2014 (530DF32A)
>> CheckSum: 000471D6
>> ImageSize: 00045000
>> File version: 0.0.0.0
>> Product version: 0.0.0.0
>> File flags: 0 (Mask 0)
>> File OS: 0 Unknown Base
>> File type: 0.0 Unknown
>> File date: 00000000.00000000
>> Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
>>
>> any idea???
>>
>> thanks
>> --
>> Enzo Cocca (PhD Candidate)
>> Research Fellow
>> Università di Napoli "L'Orientale"
>> mail: enzo.ccc at gmail.com
>> cell: +393495087014
>>
>>
>
>
> --
> Enzo Cocca (PhD Candidate)
> Research Fellow
> Università di Napoli "L'Orientale"
> mail: enzo.ccc at gmail.com
> cell: +393495087014
>
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
--
Giovanni Allegri
http://about.me/giovanniallegri
Twitter: https://twitter.com/_giohappy_
blog: http://blog.spaziogis.it
GEO+ geomatica in Italia http://bit.ly/GEOplus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140307/45685c90/attachment-0001.html>
More information about the Qgis-developer
mailing list