blocks|key|1677041|text|adb+logcat+>+logfile.txt

adb+logcat+*:E+>+logfile.txt|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1677042|如果您只想过滤错误。|unstyled|1677043|这适用于我在MS+Windows7上的操作。|1677044|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|F|7|N|8|@]|9|@]|A|$]]]|J|$]]

<pre><code>adb logcat &gt; logfile.txt

adb logcat *:E &gt; logfile.txt
</code></pre>

If you want only errors filtered.

This works for me on MS Windows 7.

blocks|key|1890954|text|不幸的是，logcat的-f选项似乎只能在安卓设备的文件系统上创建文件，而不能在开发主机上创建文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1890955|通过指定一个空文件名，很可能会导致它尝试在设备的根目录中创建一个文件，而根目录通常是不可写的。|1890956|如果您希望在设备上创建一个文件，则指定一个可写位置(适当的路径将因设备和构建而异，但以当前的示例为例)：|1890957|adb+logcat+-f+/mnt/sdcard/log.txt|code-block|syntax|javascript|1890958|作为进一步的解释，实验表明，键入adb+logcat会导致执行设备上的/system/bin/logcat程序，这与键入adb+shell+logcat时发生的情况类似。ADB可以简单地将该程序的标准或错误输出传递回主机，但设备上运行的程序无法使用设备端API来要求ADB在开发计算机上创建文件。可以在开发机器上运行的ADB部分中实现保存到文件和旋转操作，但这不是目前的工作方式。|1890959|bonitarunner的解决方案是在开发机器上使用shell重定向，这是一个简单的答案。应该可以想出一个主机端过滤器程序或脚本，实现类似于-r和-n选项的限制和旋转功能。|1890960|entityMap^0|5|6|C|2|0|0|0|0|G|A|Z|I|1O|G|0|1Y|2|21|2|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|11|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|T|$]]

Unfortunately, the <code>-f</code> option to <code>logcat</code> appears to be only able to create files on the file system of the android device and not on the development host.

By specifying a bare filename, you were most likely causing it to try to create a file in the device's root directory, which is not normally writeable. 

If you wish to create a file on the device, then specify a writable location (appropriate paths will vary by device and build, but to take a current example):

<pre><code>adb logcat -f /mnt/sdcard/log.txt
</code></pre>

By way of further explanation, experiment shows that typing <code>adb logcat</code> causes the <code>/system/bin/logcat</code> program on the device to be executed, similarly to what happens if you type <code>adb shell logcat</code>. ADB can trivially pass the standard or error output from this program back to the host machine, but there is no device-side API which a program running on the device could use to ask ADB to create files on the development machine. It would be possible for the save-to-file and rotation operations to be implemented in the portion of ADB which runs on the development machine, but that is not how it presently works.

bonitarunner's solution using a shell redirect on the development machine is a simple answer. It should be possible to come up with a host-side filter program or script which would implement limiting and rotation functionality similar to the <code>-r</code> and <code>-n</code> options.

blocks|key|1890999|text|使用adb+logcat+-d+>+log.txt|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1891000|这将把日志写到您的开发机器上。|1891001|entityMap^0|2|N|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Use <code>adb logcat -d &gt; log.txt</code>

This will write the logs on to your development machine.

On windows (win7), debugging a real phone via USB I want to dump the logcat log into a file on my PC. The rate of data is beyond what is usable in eclipse; and I want the whole unfiltered log.

According to the <a href="http://developer.android.com/tools/debugging/debugging-log.html#startingLogcat" rel="noreferrer">logcat command line instructions</a> this should be trivial with

<code>logcat -f logfile.txt</code>

I'm using <code>adb logcat -f logfile.txt</code> on the windows command line

but this always responds with 

<code>couldn't open output file: Read-only file system</code>

The file system is not read-only. Creating and writing files there works fine, and a crude redirection such as <code>adb logcat &gt; logfile.txt</code> also works as expected. Providing the whole path to the log file makes no difference.

I'd like to make use of logcat's <code>-n</code> and <code>-r</code> options but they require <code>-f</code> to work.

Any suggestions?

<hr>

Notes.
This question is close to <a href="https://askubuntu.com/questions/441167/couldnt-open-output-file-read-only-file-system">one asked on Ubuntu</a> but that has no answers that are useful to me on Windows, and one suggestion that I've already tried and doesn't work. Most similar references on SO simply quote the help page, saying <code>-f filename</code> should work.

Question edited to keep it up to date with useful comments &amp; responses.

adb logcat -f log.txt error: couldn't open output file: Read-only file system

日志文件

文件系统

Windows

在windows (win7)上，通过USB调试真实的电话我想将logcat日志转储到我PC上的一个文件中。数据的速率超出了eclipse的可用范围；我想要完整的未过滤日志。根据，这应该是微不足道的logcat -f logfile.txt我在windows命令行上使用adb logcat -f logfile.txt...

问adb logcat -f log.txt错误:无法打开输出文件:只读文件系统
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问adb logcat -f log.txt错误:无法打开输出文件:只读文件系统EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问adb logcat -f log.txt错误:无法打开输出文件:只读文件系统
EN