Grep recursive sunos11/4/2023 The very latest version is passing all existing tests and not I've been writing this post during the agonizingly slow recompiles, and We don't need to do this thanks to the magic of futexes. To HEAD is dealing with releasing the memory allocated for the pthreadĬondition variable / mutex pair that constitutes a lutex. The main issue that needs to be solved before this work can be merged In contrast to the debugger suckage, it's great to have tracing toolsĪnd the much-hyped dtrace turned out to be pretty useful in figuring out (An issue with the semantics of the x86 single-step flag in signal handlers, I've only had one really bizarre OS-related bug so far, and I could solveĪlso, it turned out to be my fault in the end. Mysterious crashes that Cyrus has been having on the other OSs. Doesn't make it any less annoying.īut I really shouldn't complain too much, since there have been someĪll the sadistic thread tests in the SBCL regression suite have been Versions of the tools could probably be found in /usr/xgrgle5/bin/, or These are tiny issues with non-standard or obsolete switches, and different My grep invocations seem to use the -r switch, which More often than I would've thought, before trying to use a system without But Solaris trumps the othersīy delivering at least two other debuggers that are also mostly useless Solaris is noĮxception here: both threads and signal handling are completelyīroken, as far as I can tell. It's to be expected that all non-Linux SBCL porters will complain bitterlyĪbout gdb being absolutely useless on their platforms. System uses, but which are not listed in the /proc file. Oh, and also to know the magic LDT indexes that the LDT indexes are in use, you need to read binary gunk from /proc directly The Solaris API for x86 local descriptor table access is rather disgusting. To a process on Solaris, there's no way to queue them for a specific Some signal handling suckage: you can only queue POSIX real-time signals Through with OS X and FreeBSD threads, I've had pretty smooth sailing '/sample/string in/strings file/title.jsp'Īnd have also tried putting single and double quotes in the scripts:įor h in "`cat strings.txt`" do echo "**$h**" grep -rl "$h" /path/to/search/ > results.txt doneĪnd the echo still shows the string being split into 3 smaller strings.Over the last few weeks I've been working on adding thread support "/sample/string in/strings file/title.jsp" I've tried putting the string in strings.txt in both single and double quotes: The cat (and grep -f) is breaking it up into: The strings in strings.txt are getting broken up into smaller strings - which I verified by putting that echo in on the grep script. The grep and the find are working fine, it's the `cat` that is giving me trouble. I need the files that contain the strings I'm searching - which I realize I didn't state clearly initially.įor h in `cat strings.txt` do echo "**$h**" grep -rl $h /path/to/search/ > results.txt doneįor h in `cat strings.txt` do find /path/to/search/ -name \*xml -exec grep -l "$h" \ > results.txt done The results going to the results.txt are the actual contents of the files, and they are not matching my string fully. I got it to work but it's not producing the results I need.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |