grepWin 1.6.14 crashes when being used in part of a script
A powerful and fast search tool using regular expressions
Brought to you by:
steveking
My PowerSehell script calls grepWin such that:
$GepWinArgumentList = """/searchpath:"".$ParsedLogDir"" /k:yes /size:-1 /searchfor:""\^M"" /regex:yes /replacewith:""\r\n"" /executeReplace /closedialog" $GrepWinProc = Start-Process $PathToGrepWin -ArgumentList "$GepWinArgumentList" -PassThru
This works file in grepWin 1.6.13 and previous, but in 1.6.14, grepWin crashes. Here are a couple of Applicaiton Event logs. Let me know if you want me to pull any additional files.
Log Name: Application Source: Application Error Date: 29/08/2016 16:22:54 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: HPElitebook Description: Faulting application name: grepWin.exe, version: 1.6.14.673, time stamp: 0x57a733f7 Faulting module name: grepWin.exe, version: 1.6.14.673, time stamp: 0x57a733f7 Exception code: 0xc0000005 Fault offset: 0x00000000000368f5 Faulting process ID: 0x1e44 Faulting application start time: 0x01d202093655cf83 Faulting application path: C:\Program Files\grepWin\grepWin.exe Faulting module path: C:\Program Files\grepWin\grepWin.exe Report ID: 21b1dcf4-4199-4b85-99ce-59f33abd92a0 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-08-29T15:22:54.279016100Z" /> <EventRecordID>7033</EventRecordID> <Channel>Application</Channel> <Computer>HPElitebook</Computer> <Security /> </System> <EventData> <Data>grepWin.exe</Data> <Data>1.6.14.673</Data> <Data>57a733f7</Data> <Data>grepWin.exe</Data> <Data>1.6.14.673</Data> <Data>57a733f7</Data> <Data>c0000005</Data> <Data>00000000000368f5</Data> <Data>1e44</Data> <Data>01d202093655cf83</Data> <Data>C:\Program Files\grepWin\grepWin.exe</Data> <Data>C:\Program Files\grepWin\grepWin.exe</Data> <Data>21b1dcf4-4199-4b85-99ce-59f33abd92a0</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
Log Name: Application Source: Windows Error Reporting Date: 29/08/2016 16:22:59 Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: HPElitebook Description: Fault bucket 120527166089, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: grepWin.exe P2: 1.6.14.673 P3: 57a733f7 P4: grepWin.exe P5: 1.6.14.673 P6: 57a733f7 P7: c0000005 P8: 00000000000368f5 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E9D.tmp.WERInternalMetadata.xml \\?\C:\Users\swin.HPELITEBOOK\AppData\Local\Temp\WER3B12.tmp.appcompat.txt triagedump.dmp \\?\C:\Users\me\AppData\Local\Temp\WER3C9A.tmp.WERDataCollectionFailure.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_grepWin.exe_cadc6e912e7f161338252e354ccc28a8958511_12d07401_096c4198 Analysis symbol: Rechecking for solution: 0 Report ID: 21b1dcf4-4199-4b85-99ce-59f33abd92a0 Report Status: 4104 Hashed bucket: 229a877aeb913629013af0b306424fc9 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-08-29T15:22:59.690358800Z" /> <EventRecordID>7034</EventRecordID> <Channel>Application</Channel> <Computer>HPElitebook</Computer> <Security /> </System> <EventData> <Data>120527166089</Data> <Data>4</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>grepWin.exe</Data> <Data>1.6.14.673</Data> <Data>57a733f7</Data> <Data>grepWin.exe</Data> <Data>1.6.14.673</Data> <Data>57a733f7</Data> <Data>c0000005</Data> <Data>00000000000368f5</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E9D.tmp.WERInternalMetadata.xml \\?\C:\Users\me\AppData\Local\Temp\WER3B12.tmp.appcompat.txt triagedump.dmp \\?\C:\Users\me\AppData\Local\Temp\WER3C9A.tmp.WERDataCollectionFailure.txt</Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_grepWin.exe_cadc6e912e7f161338252e354ccc28a8958511_12d07401_096c4198</Data> <Data> </Data> <Data>0</Data> <Data>21b1dcf4-4199-4b85-99ce-59f33abd92a0</Data> <Data>4104</Data> <Data>229a877aeb913629013af0b306424fc9</Data> </EventData> </Event>
I'm sorry, but I can't reproduce this crash. I've tried using the normal console and also your powershell script, but on my machine here I don't get a crash.
Do you have maybe more info on what I should try?
I will close this bug out. I can't reproduce this is 1.6.16, but I can now not get the command to fire. Proablaby me doing somethign wrong in systax in PS