In [Bug 582750] Tom Parker said:
(In reply to comment #2)
> Are their equivalent instructions for Windows users?
Not currently, although this should probably be fixed.
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg has a
guide that might help as a starting point (ignore the section about downloading
symbols from the Mozilla symbol server, but everything else should be usable).
In 2.7 (gimp-2.7.0-git-20090507-save-plus-export-2009-05-06-i686-setup)
it crashes when Text Tool selected as soon as I click in an image
window. (Known problem - I just wanted to try generating the mythical
windows <grin> stack trace)
Question: assuming this *were* a problem worth filing a Bug against is
any of the following any use?
Any suggestions for providing anything else necessary to actually debug
the problem?
Note: In February Jernej said to me in:
http://www.gimpusers.com/forums/gimp-user/11148-Gimp-w32-unstable-releases-2-7-was-Logo-scripts-crash-gimp-2-7.html#msg50540
> All unstable releases of GIMP (those, that have "I won't bug
> developers" checkbox) are unstripped, and should contain debugging
> symbols (though I think I forgot to remove -O2 from CFLAGS for the
> current 2.7.0 build - I'll provide another build soon).
I thought (hoped) that this would avoid the messages below like:
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for C:\WINDOWS\system32\ntdll.dll
=====================
When not debugging this generates an error dialog:
Microsoft Visual C++ Runtime Library
---------------------------
Runtime Error!
Program: D:\Program Files\GIMP-2.0\GIMP-2.7\bin\gimp-2.7.exe
This application has requested the Runtime to terminate it in an
unusual way.
Clicking [OK] closes the dos-box and gimp with no offer to debug.
so testing under windbg ....
I ran Gimp 2.7 and opened an image.WindowZ
In windbg I attached to the process and selected:
[Debug-Go unhandled exception] and
[Window-Automatically Open Disassembly]
It immediately puts this in the windbg command window:
ModLoad: 70780000 70789000 D:\Program
Files\GIMP-2.0\GIMP2.6.6\lib\gimp\2.0\modules\libdisplay-filter-lcms.dll
ModLoad: 705c0000 705f0000 D:\Program
Files\GIMP-2.0\GIMP-2.7\bin\liblcms-1.dll
ModLoad: 66f00000 66f09000 D:\Program
Files\GIMP-2.0\GIMP2.6.6\lib\gimp\2.0\modules\libcolor-selector-cmyk.dll
ModLoad: 66700000 66709000 D:\Program
Files\GIMP-2.0\GIMP2.6.6\lib\gimp\2.0\modules\libcolor-selector-water.dll
ModLoad: 62cc0000 62cc8000 D:\Program
Files\GIMP-2.0\GIMP2.6.6\lib\gimp\2.0\modules\libcolor-selector-wheel.dll
(18e8.254): Break instruction exception - code 80000003 (first chance)
eax=7ffde000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004
edi=00000005
eip=7c90120e esp=0699ffcc ebp=0699fff4 iopl=0 nv up ei pl zr
na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for C:\WINDOWS\system32\ntdll.dll -
ntdll!DbgBreakPoint:
7c90120e cc int 3
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
0:007> gn
I'm not sure what its looking for in:
"D:\Program
Files\GIMP-2.0\GIMP2.6.6\lib\gimp\2.0\modules\libcolor-selector-water.dll"
Does this indicate a setup error of some kind - maybe because (as a
result of another Bugzilla thread) I just switched to using the same set
of setup files for all gimp-2.x programs? so probably a red herring?
As soon as I click in the image window with the Text tool I get the
above [Microsoft Visual C++ Runtime Library Runtime Error!] error dialog.
At this point the following lines are added to the windbg command window:
eax=00257198 ebx=00000000 ecx=00000000 edx=00250608 esi=7c90de6e
edi=00000003
eip=7c90e514 esp=0023f054 ebp=0023f150 iopl=0 nv up ei pl zr
na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00200246
ntdll!KiFastSystemCallRet:
7c90e514 c3 ret
This is the first page shown in the [Dissasembly] window with the
indicated line selected when it opens:
<=== selected line when Disassembly window opens
Offset: @$scopeip
7c90e4e9 c744240800000000 mov dword ptr [esp+8],0
7c90e4f1 c744241000000000 mov dword ptr [esp+10h],0
7c90e4f9 54 push esp
7c90e4fa e829000000 call ntdll!RtlRaiseException (7c90e528)
7c90e4ff 8b0424 mov eax,dword ptr [esp]
7c90e502 8be5 mov esp,ebp
7c90e504 5d pop ebp
7c90e505 c3 ret
7c90e506 8da42400000000 lea esp,[esp]
7c90e50d 8d4900 lea ecx,[ecx]
ntdll!KiFastSystemCall:
7c90e510 8bd4 mov edx,esp
7c90e512 0f34 sysenter
ntdll!KiFastSystemCallRet:
7c90e514 c3 ret <=== selected line when Disassembly
window opens
7c90e515 8da42400000000 lea esp,[esp]
7c90e51c 8d642400 lea esp,[esp]
ntdll!KiIntSystemCall:
7c90e520 8d542408 lea edx,[esp+8]
7c90e524 cd2e int 2Eh
7c90e526 c3 ret
7c90e527 90 nop
ntdll!RtlRaiseException:
7c90e528 55 push ebp
7c90e529 8bec mov ebp,esp
7c90e52b 9c pushfd
7c90e52c 81ecd0020000 sub esp,offset
<Unloaded_e-buffer.dll>+0x26f (000002d0)
This is what I have at the end of the log file generated:
many lines not shown ...
hFile: 1e4 base: 7c9c0000
hFile: 1dc base: 7e410000
*** Exit process
Process exited: 124c.1d18, code 3
eax=00257198 ebx=00000000 ecx=00000000 edx=00250608 esi=7c90de6e
edi=00000003
eip=7c90e514 esp=0023f054 ebp=0023f150 iopl=0 nv up ei pl zr
na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00000246
ntdll!KiFastSystemCallRet:
7c90e514 c3 ret
Loading symbols for 7c800000 C:\WINDOWS\system32\kernel32.dll ->
C:\WINDOWS\system32\kernel32.dll
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for C:\WINDOWS\system32\kernel32.dll -
--
Regards ... Alec (bura...@gmail & WinLiveMess - alec.m.burg...@skype)
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
