Re: findstr doesn't always find
- From: foxidrive <gotcha@xxxxxxxxxxxxxx>
- Date: Tue, 27 Feb 2007 21:08:14 +1100
On 26 Feb 2007 09:23:46 -0800, "jkwold" <jkwold@xxxxxxxxxx> wrote:
I'm converting 300+ MSVC6 projects to VS2005 and fighting with .def
files (hooray for APIs and customers !) and the changes in mangled
names (particularly for CString :-) -- I've been depending on findstr
for much of the analysis, and just today found a case where the search
string wasn't always found. The string in question is:
?Initialize@CYpsBrowseIncludeDataDlg@@QAEXW4BrowseType@1@AAV?
$CStringT@GV?$StrTraitMFC_DLL@GV?$ChTraitsCRT@G@ATL@@
Note that that's not a full mangled name; I haven't found the actual
limit, but have taken to truncating strings longer than 115 chars as
findstr fails somewhere beyond that -- trivia. I'm launching findstr
as follows:
findstr /g:SR_req'd *def
JFTR find has a larger buffer (of 1025 characters) than findstr, but is not
as capable, obviously.
.
- References:
- findstr doesn't always find
- From: jkwold
- findstr doesn't always find
- Prev by Date: Re: findstr doesn't always find
- Next by Date: Re: Redirecting command output to environment variable and tracking errorlevel
- Previous by thread: Re: findstr doesn't always find
- Index(es):
Relevant Pages
|
Loading
