if you are using the Linux operating system, just open it with the less command:
less test.log
Under
windows, you can try start command:
start test.log
of course, there is also a general more command:
more test.log
isn't it sublime text??
I think we can try it. After all,
written by CPP or write a file segmentation tool yourself. Anyway, your log files are in behavior units, such as 10,000 behavior units. Split the log file into several files
and then analyze and retrieve the problem
ultraedit one by one, but you can definitely open it, but you can analyze this with the naked eye?
usually locates the problem first through tools such as linux's grep
awk
head
tail
. I don't know much about the windows tool chain, and I haven't used it.
.
< H1 > Notepad2 < / H1 >
Open a log file with Editplus yesterday, 1.02G. Editplus died on the spot.
opened successfully with notepad2. It's just that the high-occupancy software is automatically turned off. Like Chrome/idea.
the development machine stores 8G, i5 and SSD.
of course, it is recommended that you first use git-bash to filter out the key content using grep.
recommend atom . Sometimes you can use it to view a large server log
.