On 29 December 2010 04:47, Susan Cragin susancragin@earthlink.net wrote:
Stack dump: 0x000000000022b470: 0000000000000000 0000000000000000 0x000000000022b480: 0000000000000000 0000000000000000 0x000000000022b490: 0000000000000000 0000000000000000 0x000000000022b4a0: 0000000000000000 0000000000000000 0x000000000022b4b0: 0000000000000000 0000000000000000
[snip]
Backtrace: =>0 0x00007f3a9dd5cafb PathIsUNCW+0x7b() in shlwapi (0x000000000022b860)
The stack has been blitzed? Or is this local variables (even though PathIsUNCW doesn't have any)? It's hard to know what's going on without a proper stack trace. PathIsUNCW is such a small function, the problem is almost certainly further up the call chain.
Well, anybody up for seeing a couple of thousand lines of WINEDEBUG-+all, or should I run relay only?
There used to be a place to post log files so people could look at them... but I've forgotten where it is.
I was not able to reproduce this here on openSUSE 11.3, using Notepad2-4.1.24-x86-64.zip from http://www.flos-freeware.ch/notepad2.html
Is this the one you used?
The sourcecode shows it calling PathIsUNCW just with a stackbuffer in src/Dialog.c, which should be safe.
Ciao, Marcus
That is the one I used. To be clear about what I did, that file on the download site is an installation exe. I opened the compressed file and just used the program's exe and ini files by copying them to my home directory. I have compiled three logs, all, seh & relay, and have compressed them, and a copy of the program and ini file I used, and have downloaded all to the following. https://www.yousendit.com/download/RlRxT20zT2JYSHhjR0E9PQ I did not configure any special compiler optimizations. I am running Ubuntu's Natty 64-bit Studio with linux 2.6.37-11-generic.