FFIND goes crazy

#1
I issued
Code:
FFIND /s /t"setcopy" *
in a directory whose tree contains 710 files totalling about 10MB. After a lot of beeping (I figure FFIND was looking in binaries) it started to spew out empty lines. It did that for about four minutes before I pressed Ctrl-C. When I pressed Ctrl-C I got a somewhat odd "TCC has stopped working" ... odd in the sense that where it typically says "Close the program" it said instead "Restart the program". Here are the details of the crash.
Code:
Problem signature:
  Problem Event Name:    BEX
  Application Name:    tcc.exe
  Application Version:    14.0.2.37
  Application Timestamp:    50569e7a
  Fault Module Name:    StackHash_8c70
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Offset:    00200040
  Exception Code:    c0000005
  Exception Data:    00000008
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    8c70
  Additional Information 2:    8c70c0d24494ecaba6eed76d21ad285f
  Additional Information 3:    43c2
  Additional Information 4:    43c24dad54fa7b2c6f61e48a5acc43c1
I tried again pressing Ctrl-C after only 10-15 seconds of blank lines. Again I got "TCC has stopped working" ... this time with the typical "Close the program" and these details.
Code:
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    tcc.exe
  Application Version:    14.0.2.37
  Application Timestamp:    50569e7a
  Fault Module Name:    KERNELBASE.dll
  Fault Module Version:    6.1.7601.17651
  Fault Module Timestamp:    4e2111c0
  Exception Code:    e06d7363
  Exception Offset:    0000d36f
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    5180
  Additional Information 2:    5180446dbb38f0583f4e58a9918430e6
  Additional Information 3:    e0ec
  Additional Information 4:    e0ecef2b2cd665db527d109a0621e5b8
 

rconn

Administrator
Staff member
May 14, 2008
10,506
94
#2
I issued
Code:
FFIND /s /t"setcopy" *
in a directory whose tree contains 710 files totalling about 10MB. After a lot of beeping (I figure FFIND was looking in binaries) it started to spew out empty lines. It did that for about four minutes before I pressed Ctrl-C. When I pressed Ctrl-C I got a somewhat odd "TCC has stopped working" ... odd in the sense that where it typically says "Close the program" it said instead "Restart the program". Here are the details of the crash.
Not reproducible here. What happens if you add the /H option?

The details aren't useful, as the crashes are occurring in Microsoft's code. Do you have a TCC.GPF file?
 
#3
There's no GPF file. And it definitely depends *where* you do it. I was doing it in my project directory for TCSH (lots of OBJs and one or two EXEs). No doubt the text is in at least one OBJs. That would account for all the garbage and beeping, but not for the subsequent behavior I reported. If you want to try it with that exact set of files, I zipped up the directory and put it here: ftp://lucky.syr.edu/TCSH-build.zip.

The command was
Code:
ffind /s /t"setcopy" *
 
May 30, 2008
212
1
#8
I have no idea -- I couldn't reproduce the problem, so I didn't do anything to fix it.

I did add a check for the bell character (& replaced it with a space) when writing to the console.
So the PC speaker will no longer go crazy if you happen to FFIND some binary files by mistake?

That has always annoyed me, but I've been so used to it back from the DOS days, I never considered it could be fixed!
 
#9
TCC 14.02.41 Windows XP [Version 5.1.2600]
TCC Build 41 Windows XP Build 2600 Service Pack 3

Code:
[C:\Docume~1\qcmsb0]
13:42:49 $ ffind /t"autocrlf" /s *
 
---- C:\Docume~1\qcmsb0\.netbeans\7.0\modules\ext\org.eclipse.jgit-1.0.0.201106090707-r.jar
org/eclipse/jgit/lib/CoreConfig$AutoCRLF.classòS∩O╙P¶=Ñ█┌ò┬pⁿÿ èΓÉv‼╩T⌠♥♂a╬═`→0t#!~Ωµcv)¡ΘZ■.↓ë↑ìå╧■Q╞√╩"►ëB¢£√╬φ╜τ▐√▐δ╧
__⌂ (ßà♀YFZå"@╩∩V╠f═↕ j·« ╣▄v↔╧ ╫♣ñ╩âE▓^1¡→┘═¡╖═åÇDcºI┤°╬⌠âÄ┴(ßcÅ↓▌Ä‼→«╙2¬~└¬╛╖∩t≥ò(⌠½;f}ìÆ█«∩1☺ú]√╨6\█δ↑5/: 5╧>  ▄⌂┤♦h╫
¡FÜߺG├↔┌n─╢≈iûx╒ô0,aDBF┬ÿǼy▐ï§♠Ä╫í>♂7↓¬l^₧ª|²ΣuJƒ╨⌠♂☻█¡.kçΣ₧╥■nlô▼╬ƪ▀h╧╫»►╥o"░zQáΩ┌╜▐┌Uèù7aMàîi§i♫
^C
It still beeps.