Crash with some filenames with /q

[GoogleCodeExporter]

What steps will reproduce the problem?
0. Prepare:
- Make sure you've got C: and D: letters (or you can just
> subst D: C:\
if you don't)

- Put attached notepad2-TC.ini to c:\Program Files\Total Commander\notepad2.ini 
(not just put to the directory, rename it no notepad2.ini)
- Put notepad2.exe to same dir (c:\Program Files\Total Commander)
- Put attached Notepad2.ini to %APPDATA%\Notepad2\Notepad2.ini
- Create directory d:\Projects\Google Forms

1. Create file "d:\Projects\Google Forms\Автозаполнение.ahk" (
> echo.>"d:\Projects\Google Forms\Автозаполнение.ahk"
). Note that path and filename must be exact.

2. Open it with command
"c:\Program Files\Total Commander\notepad2.exe" /q "D:\Projects\Google 
Forms\Автозаполнение.ahk"
Note that Notepad2 must be there. Effect does not appear if Notepad2 is on 
other path or without /q switch.

3. Try anything – change and save, select encoding, even just press F1.

What is the expected output? What do you see instead?
Expected is not crash.
I'm getting crash.

What version of the product are you using? On what operating system?

Notepad2 ver. 4.2.25 rev.720. WinXP SP3+last updates.

Please provide any additional information below.

Happened with other versions and other filenames, not always with unicode 
characters. I just wasn't that bored to fill in an issue.

Error signature:
AppName: notepad2.exe    AppVer: 4.2.25.720  ModName: notepad2.exe
ModVer: 4.2.25.720   Offset: 000aa60f

Windows Crash report text and Notepad 2 config file attached.

Original issue reported on code.google.com by antic...@mobilmir.ru on 18 Apr 2012 at 6:50

Attachments:

• crash-info.txt
• notepad2-TC.ini
• Notepad2.ini

[GoogleCodeExporter]

Does it happen with the official Notepad2? You can try a debug build and see if 
you can get more info about the crash.

Original comment by XhmikosR on 18 Apr 2012 at 6:55

[GoogleCodeExporter]

1. As I'm using mod quite long time, I am not sure about official version.
And command line causing crash depends on version, so if some specific causing 
crash with ICL build, it won't do so with WDK build, crash-names for WDK build 
will differ.

2. I've got no development tools on my work notebook. Where can I get current 
debug build?

Original comment by antic...@mobilmir.ru on 19 Apr 2012 at 11:50

[GoogleCodeExporter]

Well you should try Notepad2 with your setup and paths and see if it's crashing.
As for a debug build I could provide you one. 32bit or 64bit? If it crahses you 
will have to search for .dmp files and upload it somewhere for me.

Original comment by XhmikosR on 21 Apr 2012 at 3:01

[GoogleCodeExporter]

I'm here with unfortunate news. It don't crash with this file anymore. Not sure 
is this due to recent-files-list update in ini file or smth else.

Still, it happens time to time with different files, so if you'll provide 
32-bit debug build, I'll post dumps once it crashes next time.

Original comment by antic...@mobilmir.ru on 23 Apr 2012 at 5:25

[GoogleCodeExporter]

That happened several times from that date (after I updated to 4.2.25.735 too).

Sometimes it even happened after several edits and saves, or after Ctrl+L.

I don't mean to nag you, but I'm waiting for availability of precompiled debug 
version.

Original comment by antic...@mobilmir.ru on 8 May 2012 at 9:12

[GoogleCodeExporter]

Providing you with a debug build doesn't mean the problem will magically be 
fixed. And I can't fix it anyway. You have to find out if the crash happens 
with Notepad2 and not only Notepad2-mod or if it happens only with ICL12 builds 
or with WDK builds too.

Either way, I doubt it will be something I could fix.

Original comment by XhmikosR on 8 May 2012 at 9:15

[GoogleCodeExporter]

I understand, but debug information could be helpful. At least it could point 
to specific function, which can help reproduce the crash.

It happend with ICL builds more often for me when with WDK. I walked off ICL 
builds because of it.

To find if crash happens with original Notepad2, I'll have to get to using it 
instead of -mod (because unfortunately I've got no stable crash scenario). 
Well, I'll do it, sooner or later.

One thing I found, that with Winspector Spy running it crashes more often, and 
if it crashes with some file, without Spy it don't (but crashes with other).

Original comment by antic...@mobilmir.ru on 8 May 2012 at 11:03