Re: [android-beginners] Re: LogCat
I always use this http://www.adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx BR, Adrian Vintu http://adrianvintu.com On Wed, Jun 30, 2010 at 6:31 PM, DonFrench wrote: > Thank you! > > On Jun 27, 12:29 am, Indicator Veritatis wrote: > > That was completely uncalled for and even completely unjustifiable. > > Why, your own response is more like that of "a petulant child" than > > any thingDonFrenchsaid. > > > > After all Don French gave an excellent list of reasons why it is > > better to view DDMS LogCat output in Eclipse rather than running it > > standalone. What is more, he showed very much the opposite of the > > petulance you so unfairly accuse him of by patiently detailing all > > these advantages of viewing in Eclipse. > > > > Real software professionals recognize your "fix it yourself" as the > > real petulance, since real software engineers understand that such > > bugs should be fixed by the person(s) most familiar with that part of > > the code. "Code diving" is all too often a terrible waste of a good > > engineer's time. Worse yet, it often causes other bugs down the road, > > because the 'diver' did not understand the code well enough. This is > > WHY it should be fixed by the person(s) most familiar with the > > relevant code, not by anyone who feels the need for the fix. > > > > Personally, I hope Google's team will find the time to fix it > > relatively soon, but I am not going to sweat it if they don't. But I > > will join Don in saying that it would be a valuable fix, it is likely > > being given too low a priority -- as often happens even in the best- > > run projects. > > > > Finally, if the Google team does recognize this as a bug, how do we > > find it in the bug database? Some of us would like to vote for it;) > > > > On Jun 23, 6:08 pm, Mikey wrote: > > > > > Spoken like a petulant child - fix it yourself if you think you can do > better... > > > > > On 24 Jun 2010, at 01:06,DonFrenchwrote:> Thanks but I really prefer to > view LogCat in Eclipse because it is so > > > > much easier to find what you want. In Eclipse, for example, user- > > > > generated log output is split into individual tabs based on the tags > > > > you set. Also, in the main log tab everything is color coded. To > > > > find the stack trace associated with a Force Close, for example, you > > > > just scroll up until you see a block of red output. Google did a > > > > great job in designing the Eclipse LogCat viewer except for the > > > > unfortunate bug that they have ignored for so long. > > > > > > On Jun 22, 11:11 am, Kostya Vasilyev wrote: > > > >> Don, > > > > > >> I can recommend running "adblogcat" from the OS's command line > window. > > > > > >> This way, it's always around, you can make it as large as you want, > and > > > >> can do filtering by piping through grep or find, if necessary. > > > > > >> -- Kostya > > > > > >> 22.06.2010 22:02,DonFrenchпишет: > > > > > >>> I useLogCata lot when debugging but it is an ir ritation that it > > > >>> frequently has to be reset to get the latest log output. I am only > > > >>> aware of two ways to get the log output when this happens: 1) Go to > > > >>> the DDMS perspective and then pull down the menu in the Devices > view > > > >>> and select reset adb, and 2) Exit Eclipse and restart it. Some of > the > > > >>> time Reset adb works but often it does not and I have to exit and > > > >>> restart Eclipse. So, first, am I doing something wrong that causes > > > >>> LogCatto stop functioning? And second, is there another way to > > > >>> refresh the log other than the two methods I mentioned? And third, > is > > > >>> this a bug in the Android Eclipse plug-in? If it is, why doesn't > > > >>> Google fix it? > > > > > >> -- > > > >> Kostya Vasilev -- WiFi Manager + pretty widget -- > http://kmansoft.wordpress.com > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Android Beginners" group. > > > > > > NEW! Try asking and tagging your question on Stack Overflow at > > > >http://stackoverflow.com/questions/tagged/android > > > > > > To unsubscribe from this group, send email to > > > > android-beginners+unsubscr...@googlegroups.com > > > > For more options, visit this group at > > > >http://groups.google.com/group/android-beginners?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To
[android-beginners] Re: LogCat
Thank you! On Jun 27, 12:29 am, Indicator Veritatis wrote: > That was completely uncalled for and even completely unjustifiable. > Why, your own response is more like that of "a petulant child" than > any thingDonFrenchsaid. > > After all Don French gave an excellent list of reasons why it is > better to view DDMS LogCat output in Eclipse rather than running it > standalone. What is more, he showed very much the opposite of the > petulance you so unfairly accuse him of by patiently detailing all > these advantages of viewing in Eclipse. > > Real software professionals recognize your "fix it yourself" as the > real petulance, since real software engineers understand that such > bugs should be fixed by the person(s) most familiar with that part of > the code. "Code diving" is all too often a terrible waste of a good > engineer's time. Worse yet, it often causes other bugs down the road, > because the 'diver' did not understand the code well enough. This is > WHY it should be fixed by the person(s) most familiar with the > relevant code, not by anyone who feels the need for the fix. > > Personally, I hope Google's team will find the time to fix it > relatively soon, but I am not going to sweat it if they don't. But I > will join Don in saying that it would be a valuable fix, it is likely > being given too low a priority -- as often happens even in the best- > run projects. > > Finally, if the Google team does recognize this as a bug, how do we > find it in the bug database? Some of us would like to vote for it;) > > On Jun 23, 6:08 pm, Mikey wrote: > > > Spoken like a petulant child - fix it yourself if you think you can do > > better... > > > On 24 Jun 2010, at 01:06,DonFrenchwrote:> Thanks but I really prefer to > > view LogCat in Eclipse because it is so > > > much easier to find what you want. In Eclipse, for example, user- > > > generated log output is split into individual tabs based on the tags > > > you set. Also, in the main log tab everything is color coded. To > > > find the stack trace associated with a Force Close, for example, you > > > just scroll up until you see a block of red output. Google did a > > > great job in designing the Eclipse LogCat viewer except for the > > > unfortunate bug that they have ignored for so long. > > > > On Jun 22, 11:11 am, Kostya Vasilyev wrote: > > >> Don, > > > >> I can recommend running "adblogcat" from the OS's command line window. > > > >> This way, it's always around, you can make it as large as you want, and > > >> can do filtering by piping through grep or find, if necessary. > > > >> -- Kostya > > > >> 22.06.2010 22:02,DonFrenchпишет: > > > >>> I useLogCata lot when debugging but it is an ir ritation that it > > >>> frequently has to be reset to get the latest log output. I am only > > >>> aware of two ways to get the log output when this happens: 1) Go to > > >>> the DDMS perspective and then pull down the menu in the Devices view > > >>> and select reset adb, and 2) Exit Eclipse and restart it. Some of the > > >>> time Reset adb works but often it does not and I have to exit and > > >>> restart Eclipse. So, first, am I doing something wrong that causes > > >>> LogCatto stop functioning? And second, is there another way to > > >>> refresh the log other than the two methods I mentioned? And third, is > > >>> this a bug in the Android Eclipse plug-in? If it is, why doesn't > > >>> Google fix it? > > > >> -- > > >> Kostya Vasilev -- WiFi Manager + pretty widget > > >> --http://kmansoft.wordpress.com > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Beginners" group. > > > > NEW! Try asking and tagging your question on Stack Overflow at > > >http://stackoverflow.com/questions/tagged/android > > > > To unsubscribe from this group, send email to > > > android-beginners+unsubscr...@googlegroups.com > > > For more options, visit this group at > > >http://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: LogCat
That was completely uncalled for and even completely unjustifiable. Why, your own response is more like that of "a petulant child" than any thing DonFrench said. After all Don French gave an excellent list of reasons why it is better to view DDMS LogCat output in Eclipse rather than running it standalone. What is more, he showed very much the opposite of the petulance you so unfairly accuse him of by patiently detailing all these advantages of viewing in Eclipse. Real software professionals recognize your "fix it yourself" as the real petulance, since real software engineers understand that such bugs should be fixed by the person(s) most familiar with that part of the code. "Code diving" is all too often a terrible waste of a good engineer's time. Worse yet, it often causes other bugs down the road, because the 'diver' did not understand the code well enough. This is WHY it should be fixed by the person(s) most familiar with the relevant code, not by anyone who feels the need for the fix. Personally, I hope Google's team will find the time to fix it relatively soon, but I am not going to sweat it if they don't. But I will join Don in saying that it would be a valuable fix, it is likely being given too low a priority -- as often happens even in the best- run projects. Finally, if the Google team does recognize this as a bug, how do we find it in the bug database? Some of us would like to vote for it;) On Jun 23, 6:08 pm, Mikey wrote: > Spoken like a petulant child - fix it yourself if you think you can do > better... > > On 24 Jun 2010, at 01:06, DonFrench wrote:> Thanks but I really prefer to > view LogCat in Eclipse because it is so > > much easier to find what you want. In Eclipse, for example, user- > > generated log output is split into individual tabs based on the tags > > you set. Also, in the main log tab everything is color coded. To > > find the stack trace associated with a Force Close, for example, you > > just scroll up until you see a block of red output. Google did a > > great job in designing the Eclipse LogCat viewer except for the > > unfortunate bug that they have ignored for so long. > > > On Jun 22, 11:11 am, Kostya Vasilyev wrote: > >> Don, > > >> I can recommend running "adblogcat" from the OS's command line window. > > >> This way, it's always around, you can make it as large as you want, and > >> can do filtering by piping through grep or find, if necessary. > > >> -- Kostya > > >> 22.06.2010 22:02, DonFrench пишет: > > >>> I useLogCata lot when debugging but it is an ir ritation that it > >>> frequently has to be reset to get the latest log output. I am only > >>> aware of two ways to get the log output when this happens: 1) Go to > >>> the DDMS perspective and then pull down the menu in the Devices view > >>> and select reset adb, and 2) Exit Eclipse and restart it. Some of the > >>> time Reset adb works but often it does not and I have to exit and > >>> restart Eclipse. So, first, am I doing something wrong that causes > >>> LogCatto stop functioning? And second, is there another way to > >>> refresh the log other than the two methods I mentioned? And third, is > >>> this a bug in the Android Eclipse plug-in? If it is, why doesn't > >>> Google fix it? > > >> -- > >> Kostya Vasilev -- WiFi Manager + pretty widget > >> --http://kmansoft.wordpress.com > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Beginners" group. > > > NEW! Try asking and tagging your question on Stack Overflow at > >http://stackoverflow.com/questions/tagged/android > > > To unsubscribe from this group, send email to > > android-beginners+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
Re: [android-beginners] Re: LogCat
Spoken like a petulant child - fix it yourself if you think you can do better... On 24 Jun 2010, at 01:06, DonFrench wrote: > Thanks but I really prefer to view LogCat in Eclipse because it is so > much easier to find what you want. In Eclipse, for example, user- > generated log output is split into individual tabs based on the tags > you set. Also, in the main log tab everything is color coded. To > find the stack trace associated with a Force Close, for example, you > just scroll up until you see a block of red output. Google did a > great job in designing the Eclipse LogCat viewer except for the > unfortunate bug that they have ignored for so long. > > > On Jun 22, 11:11 am, Kostya Vasilyev wrote: >> Don, >> >> I can recommend running "adblogcat" from the OS's command line window. >> >> This way, it's always around, you can make it as large as you want, and >> can do filtering by piping through grep or find, if necessary. >> >> -- Kostya >> >> 22.06.2010 22:02, DonFrench пишет: >> >>> I useLogCata lot when debugging but it is an ir ritation that it >>> frequently has to be reset to get the latest log output. I am only >>> aware of two ways to get the log output when this happens: 1) Go to >>> the DDMS perspective and then pull down the menu in the Devices view >>> and select reset adb, and 2) Exit Eclipse and restart it. Some of the >>> time Reset adb works but often it does not and I have to exit and >>> restart Eclipse. So, first, am I doing something wrong that causes >>> LogCatto stop functioning? And second, is there another way to >>> refresh the log other than the two methods I mentioned? And third, is >>> this a bug in the Android Eclipse plug-in? If it is, why doesn't >>> Google fix it? >> >> -- >> Kostya Vasilev -- WiFi Manager + pretty widget >> --http://kmansoft.wordpress.com > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
Re: [android-beginners] Re: LogCat
We are well aware of the issues with the logcat panel in DDMS. We hope to get around to see sooner rather than later but we've got a lot of stuff on our plate unfortunately. Xav On Wed, Jun 23, 2010 at 5:06 PM, DonFrench wrote: > Thanks but I really prefer to view LogCat in Eclipse because it is so > much easier to find what you want. In Eclipse, for example, user- > generated log output is split into individual tabs based on the tags > you set. Also, in the main log tab everything is color coded. To > find the stack trace associated with a Force Close, for example, you > just scroll up until you see a block of red output. Google did a > great job in designing the Eclipse LogCat viewer except for the > unfortunate bug that they have ignored for so long. > > > On Jun 22, 11:11 am, Kostya Vasilyev wrote: >> Don, >> >> I can recommend running "adblogcat" from the OS's command line window. >> >> This way, it's always around, you can make it as large as you want, and >> can do filtering by piping through grep or find, if necessary. >> >> -- Kostya >> >> 22.06.2010 22:02, DonFrench пишет: >> >> > I useLogCata lot when debugging but it is an ir ritation that it >> > frequently has to be reset to get the latest log output. I am only >> > aware of two ways to get the log output when this happens: 1) Go to >> > the DDMS perspective and then pull down the menu in the Devices view >> > and select reset adb, and 2) Exit Eclipse and restart it. Some of the >> > time Reset adb works but often it does not and I have to exit and >> > restart Eclipse. So, first, am I doing something wrong that causes >> >LogCatto stop functioning? And second, is there another way to >> > refresh the log other than the two methods I mentioned? And third, is >> > this a bug in the Android Eclipse plug-in? If it is, why doesn't >> > Google fix it? >> >> -- >> Kostya Vasilev -- WiFi Manager + pretty widget >> --http://kmansoft.wordpress.com > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: LogCat
Thanks but I really prefer to view LogCat in Eclipse because it is so much easier to find what you want. In Eclipse, for example, user- generated log output is split into individual tabs based on the tags you set. Also, in the main log tab everything is color coded. To find the stack trace associated with a Force Close, for example, you just scroll up until you see a block of red output. Google did a great job in designing the Eclipse LogCat viewer except for the unfortunate bug that they have ignored for so long. On Jun 22, 11:11 am, Kostya Vasilyev wrote: > Don, > > I can recommend running "adblogcat" from the OS's command line window. > > This way, it's always around, you can make it as large as you want, and > can do filtering by piping through grep or find, if necessary. > > -- Kostya > > 22.06.2010 22:02, DonFrench пишет: > > > I useLogCata lot when debugging but it is an ir ritation that it > > frequently has to be reset to get the latest log output. I am only > > aware of two ways to get the log output when this happens: 1) Go to > > the DDMS perspective and then pull down the menu in the Devices view > > and select reset adb, and 2) Exit Eclipse and restart it. Some of the > > time Reset adb works but often it does not and I have to exit and > > restart Eclipse. So, first, am I doing something wrong that causes > >LogCatto stop functioning? And second, is there another way to > > refresh the log other than the two methods I mentioned? And third, is > > this a bug in the Android Eclipse plug-in? If it is, why doesn't > > Google fix it? > > -- > Kostya Vasilev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: LogCat window seems to stop working
>From your linux terminal: adb logcat To clear it: adb logcat -c Make sure you're either in your android-sdk-linux_86/tools directory or that you have it added to your path otherwise you'll get an error when you run adb. See this page for more on logcat options: http://developer.android.com/guide/developing/tools/adb.html#logcatoptions On Jan 29, 9:02 pm, Kevin Duffey wrote: > I thought about that.. starting adb from command line instead of eclipse.. > not sure how to run the logcat output from there yet, I am sure google > search will show how. I wonder if there is some issue with the IDE and > android debug/logcat that causes this to happen at times. Today, I started > my computer clean, and several tries running the emulator from the RUN > button, DEBUG button and trying to run it from the AVD window would cause my > app to never actually deploy to it. I restarted Eclipse, and all worked. It > seems to do this all the time tho. I am trying to keep track of what I do > when it fails, then works again. I am finally getting LogCat output, but > this only happens when I actually get everything working cleanly. I don't > mind restarting eclipse..only takes a few seconds, but the notion of it kind > of bugs me. Reminds me when we ran Windows as a server..every few days we > had to reboot it. > > > > On Fri, Jan 29, 2010 at 8:46 AM, KitzyKitt wrote: > > I have also noticed that hitting the clear log. Button in Eclipce will > > wipe the log and not reconnect it. Restarting Eclipse will reconnect > > the log. > > > You can try using the command line to show the log. > > > -Kitzy > > > On Jan 28, 11:20 pm, Kevin Duffey wrote: > > > Hey all, > > > > Has anyone noticed that their LogCat window seems to stop working after > > an > > > app force closes.. or maybe for some other reason? I've been having > > issues > > > getting debugging to work on my Ubuntu 9.04 64-bit system with this > > annoying > > > QEMU channel closed problem. That aside, even when things do work, it > > seems > > > that for some odd reason LogCat stops receiving..or displaying anything. > > > Even when my app works, and I redeploy it, it seems to just stop showing > > any > > > Log.v output. I did try filtering, setting to verbose, info, error, etc, > > and > > > it only seems on the first run of the app when all works fine that there > > is > > > any output. > > > > Is there some way to reconnect it? When I clear the log, it stays empty > > > until I restart Eclipse..which is quite painful to have to do every time > > I > > > want to deploy to watch log output. > > > > Thanks. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Beginners" group. > > > NEW! Try asking and tagging your question on Stack Overflow at > >http://stackoverflow.com/questions/tagged/android > > > To unsubscribe from this group, send email to > > android-beginners+unsubscr...@googlegroups.com > i...@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
Re: [android-beginners] Re: LogCat window seems to stop working
When I switch to DDMS perspective, I see that window. It's the only emulator/device running. So I would assume it's correct. I am wondering if running the emulator from command line would be better. I am going to try that as well, as it seems I get a random crap shoot when LogCat works.. as well as when my app actually works. Many times, the emulator just seems to crash before my app can be deployed when I run it from Eclipse. I am not sure why. So befoe I spend cycles on trying to figure that out, I'll try the command line adb approach and see if that helps. On Sat, Jan 30, 2010 at 8:56 AM, Marc wrote: > did you try selecting the devices tab and making sure the device is > selected. > > On Jan 28, 10:20 pm, Kevin Duffey wrote: > > Hey all, > > > > Has anyone noticed that their LogCat window seems to stop working after > an > > app force closes.. or maybe for some other reason? I've been having > issues > > getting debugging to work on my Ubuntu 9.04 64-bit system with this > annoying > > QEMU channel closed problem. That aside, even when things do work, it > seems > > that for some odd reason LogCat stops receiving..or displaying anything. > > Even when my app works, and I redeploy it, it seems to just stop showing > any > > Log.v output. I did try filtering, setting to verbose, info, error, etc, > and > > it only seems on the first run of the app when all works fine that there > is > > any output. > > > > Is there some way to reconnect it? When I clear the log, it stays empty > > until I restart Eclipse..which is quite painful to have to do every time > I > > want to deploy to watch log output. > > > > Thanks. > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: LogCat window seems to stop working
did you try selecting the devices tab and making sure the device is selected. On Jan 28, 10:20 pm, Kevin Duffey wrote: > Hey all, > > Has anyone noticed that their LogCat window seems to stop working after an > app force closes.. or maybe for some other reason? I've been having issues > getting debugging to work on my Ubuntu 9.04 64-bit system with this annoying > QEMU channel closed problem. That aside, even when things do work, it seems > that for some odd reason LogCat stops receiving..or displaying anything. > Even when my app works, and I redeploy it, it seems to just stop showing any > Log.v output. I did try filtering, setting to verbose, info, error, etc, and > it only seems on the first run of the app when all works fine that there is > any output. > > Is there some way to reconnect it? When I clear the log, it stays empty > until I restart Eclipse..which is quite painful to have to do every time I > want to deploy to watch log output. > > Thanks. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
Re: [android-beginners] Re: LogCat window seems to stop working
I thought about that.. starting adb from command line instead of eclipse.. not sure how to run the logcat output from there yet, I am sure google search will show how. I wonder if there is some issue with the IDE and android debug/logcat that causes this to happen at times. Today, I started my computer clean, and several tries running the emulator from the RUN button, DEBUG button and trying to run it from the AVD window would cause my app to never actually deploy to it. I restarted Eclipse, and all worked. It seems to do this all the time tho. I am trying to keep track of what I do when it fails, then works again. I am finally getting LogCat output, but this only happens when I actually get everything working cleanly. I don't mind restarting eclipse..only takes a few seconds, but the notion of it kind of bugs me. Reminds me when we ran Windows as a server..every few days we had to reboot it. On Fri, Jan 29, 2010 at 8:46 AM, KitzyKitt wrote: > I have also noticed that hitting the clear log. Button in Eclipce will > wipe the log and not reconnect it. Restarting Eclipse will reconnect > the log. > > You can try using the command line to show the log. > > -Kitzy > > On Jan 28, 11:20 pm, Kevin Duffey wrote: > > Hey all, > > > > Has anyone noticed that their LogCat window seems to stop working after > an > > app force closes.. or maybe for some other reason? I've been having > issues > > getting debugging to work on my Ubuntu 9.04 64-bit system with this > annoying > > QEMU channel closed problem. That aside, even when things do work, it > seems > > that for some odd reason LogCat stops receiving..or displaying anything. > > Even when my app works, and I redeploy it, it seems to just stop showing > any > > Log.v output. I did try filtering, setting to verbose, info, error, etc, > and > > it only seems on the first run of the app when all works fine that there > is > > any output. > > > > Is there some way to reconnect it? When I clear the log, it stays empty > > until I restart Eclipse..which is quite painful to have to do every time > I > > want to deploy to watch log output. > > > > Thanks. > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: LogCat window seems to stop working
I have also noticed that hitting the clear log. Button in Eclipce will wipe the log and not reconnect it. Restarting Eclipse will reconnect the log. You can try using the command line to show the log. -Kitzy On Jan 28, 11:20 pm, Kevin Duffey wrote: > Hey all, > > Has anyone noticed that their LogCat window seems to stop working after an > app force closes.. or maybe for some other reason? I've been having issues > getting debugging to work on my Ubuntu 9.04 64-bit system with this annoying > QEMU channel closed problem. That aside, even when things do work, it seems > that for some odd reason LogCat stops receiving..or displaying anything. > Even when my app works, and I redeploy it, it seems to just stop showing any > Log.v output. I did try filtering, setting to verbose, info, error, etc, and > it only seems on the first run of the app when all works fine that there is > any output. > > Is there some way to reconnect it? When I clear the log, it stays empty > until I restart Eclipse..which is quite painful to have to do every time I > want to deploy to watch log output. > > Thanks. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
RE: [android-beginners] Re: logcat question
Thank you so much Steve and Mark for your replies. It is helping me
understand how to read the logcat output better. :)
I put a breakpoint on line 42, but it still crashed when I ran it with the
breakpoint. Is that the same as a debug point?
_
From: android-beginners@googlegroups.com
[mailto:android-beginn...@googlegroups.com] On Behalf Of Stephen Abrams
Sent: Saturday, December 19, 2009 9:01 PM
To: android-beginners@googlegroups.com
Subject: Re: [android-beginners] Re: logcat question
Hi tinyang,
If you're using eclipse, you can put a debug point at line 42 in
CameraPreview and see what object is null that you're trying to call a
method on.
Steve
On Sat, Dec 19, 2009 at 3:15 PM, tinyang wrote:
OK, thanks.
-Original Message-
From: android-beginners@googlegroups.com
[mailto:android-beginn...@googlegroups.com] On Behalf Of Lance Nanek
Sent: Saturday, December 19, 2009 12:26 PM
To: Android Beginners
Subject: [android-beginners] Re: logcat question
You are already seeing them. The more refers to the lines that are just
duplicates of the lines that the RuntimeException exception above the
NullPointerException has already printed.
On Dec 19, 11:44 am, "tinyang" wrote:
> I'm trying to figure out a java.lang.RuntimeException problem in my app.
> When I look at the logcat, it will show something like this:
>
> 12-19 09:29:38.055: WARN/dalvikvm(716): threadid=3: thread exiting
> with uncaught exception (group=0x4000fe70)
> 12-19 09:29:38.065: ERROR/AndroidRuntime(716): Uncaught handler:
> thread main exiting due to uncaught exception
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): java.lang.RuntimeException:
> Unable to start activity ComponentInfo{test.app/test.app.CameraPreview}:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> 268)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:22
> 84)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.access$1800(ActivityThread.java:112)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Looper.loop(Looper.java:123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.main(ActivityThread.java:3948)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invoke(Method.java:521)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.
> java:7
> 82)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> dalvik.system.NativeStart.main(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): Caused by:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> test.app.CameraPreview.onCreate(CameraPreview.java:42)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:
> 1123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> 231)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): ... 11 more
>
> I want to see the "11 more" lines in the error logging. How do I view
> those?
>
> Thanks.
--
You received this message because you are subscribed to the Google Groups
"Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
<mailto:android-beginners%2bunsubscr...@googlegroups.com>
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.406 / Virus Database: 270.14.89/2539 - Release Date: 12/18/09
19:38:00
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
<mailto:android-beginners%2bunsubscr...@googlegroups.com>
For more options,
Re: [android-beginners] Re: logcat question
Hi tinyang,
If you're using eclipse, you can put a debug point at line 42 in
CameraPreview and see what object is null that you're trying to call a
method on.
Steve
On Sat, Dec 19, 2009 at 3:15 PM, tinyang wrote:
> OK, thanks.
>
> -Original Message-
> From: android-beginners@googlegroups.com
> [mailto:android-beginn...@googlegroups.com] On Behalf Of Lance Nanek
> Sent: Saturday, December 19, 2009 12:26 PM
> To: Android Beginners
> Subject: [android-beginners] Re: logcat question
>
> You are already seeing them. The more refers to the lines that are just
> duplicates of the lines that the RuntimeException exception above the
> NullPointerException has already printed.
>
> On Dec 19, 11:44 am, "tinyang" wrote:
> > I'm trying to figure out a java.lang.RuntimeException problem in my app.
> > When I look at the logcat, it will show something like this:
> >
> > 12-19 09:29:38.055: WARN/dalvikvm(716): threadid=3: thread exiting
> > with uncaught exception (group=0x4000fe70)
> > 12-19 09:29:38.065: ERROR/AndroidRuntime(716): Uncaught handler:
> > thread main exiting due to uncaught exception
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716):
> java.lang.RuntimeException:
> > Unable to start activity ComponentInfo{test.app/test.app.CameraPreview}:
> > java.lang.NullPointerException
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> > 268)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:22
> > 84)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread.access$1800(ActivityThread.java:112)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.os.Handler.dispatchMessage(Handler.java:99)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.os.Looper.loop(Looper.java:123)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread.main(ActivityThread.java:3948)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > java.lang.reflect.Method.invokeNative(Native Method)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > java.lang.reflect.Method.invoke(Method.java:521)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.
> > java:7
> > 82)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > dalvik.system.NativeStart.main(Native Method)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): Caused by:
> > java.lang.NullPointerException
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > test.app.CameraPreview.onCreate(CameraPreview.java:42)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:
> > 1123)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> > android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> > 231)
> > 12-19 09:29:38.075: ERROR/AndroidRuntime(716): ... 11 more
> >
> > I want to see the "11 more" lines in the error logging. How do I view
> > those?
> >
> > Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android Beginners" group.
> To post to this group, send email to android-beginners@googlegroups.com
> To unsubscribe from this group, send email to
> android-beginners+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-beginners?hl=en
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.406 / Virus Database: 270.14.89/2539 - Release Date: 12/18/09
> 19:38:00
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Beginners" group.
> To post to this group, send email to android-beginners@googlegroups.com
> To unsubscribe from this group, send email to
> android-beginners+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-beginners?hl=en
>
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
RE: [android-beginners] Re: logcat question
OK, thanks.
-Original Message-
From: android-beginners@googlegroups.com
[mailto:android-beginn...@googlegroups.com] On Behalf Of Lance Nanek
Sent: Saturday, December 19, 2009 12:26 PM
To: Android Beginners
Subject: [android-beginners] Re: logcat question
You are already seeing them. The more refers to the lines that are just
duplicates of the lines that the RuntimeException exception above the
NullPointerException has already printed.
On Dec 19, 11:44 am, "tinyang" wrote:
> I'm trying to figure out a java.lang.RuntimeException problem in my app.
> When I look at the logcat, it will show something like this:
>
> 12-19 09:29:38.055: WARN/dalvikvm(716): threadid=3: thread exiting
> with uncaught exception (group=0x4000fe70)
> 12-19 09:29:38.065: ERROR/AndroidRuntime(716): Uncaught handler:
> thread main exiting due to uncaught exception
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): java.lang.RuntimeException:
> Unable to start activity ComponentInfo{test.app/test.app.CameraPreview}:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> 268)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:22
> 84)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.access$1800(ActivityThread.java:112)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Looper.loop(Looper.java:123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.main(ActivityThread.java:3948)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invoke(Method.java:521)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.
> java:7
> 82)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> dalvik.system.NativeStart.main(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): Caused by:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> test.app.CameraPreview.onCreate(CameraPreview.java:42)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:
> 1123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2
> 231)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): ... 11 more
>
> I want to see the "11 more" lines in the error logging. How do I view
> those?
>
> Thanks.
--
You received this message because you are subscribed to the Google Groups
"Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.406 / Virus Database: 270.14.89/2539 - Release Date: 12/18/09
19:38:00
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: logcat question
You are already seeing them. The more refers to the lines that are
just duplicates of the lines that the RuntimeException exception above
the NullPointerException has already printed.
On Dec 19, 11:44 am, "tinyang" wrote:
> I'm trying to figure out a java.lang.RuntimeException problem in my app.
> When I look at the logcat, it will show something like this:
>
> 12-19 09:29:38.055: WARN/dalvikvm(716): threadid=3: thread exiting with
> uncaught exception (group=0x4000fe70)
> 12-19 09:29:38.065: ERROR/AndroidRuntime(716): Uncaught handler: thread main
> exiting due to uncaught exception
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): java.lang.RuntimeException:
> Unable to start activity ComponentInfo{test.app/test.app.CameraPreview}:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2268)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2284)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.access$1800(ActivityThread.java:112)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Handler.dispatchMessage(Handler.java:99)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.os.Looper.loop(Looper.java:123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.main(ActivityThread.java:3948)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invokeNative(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> java.lang.reflect.Method.invoke(Method.java:521)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:7
> 82)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> dalvik.system.NativeStart.main(Native Method)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): Caused by:
> java.lang.NullPointerException
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> test.app.CameraPreview.onCreate(CameraPreview.java:42)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): at
> android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2231)
> 12-19 09:29:38.075: ERROR/AndroidRuntime(716): ... 11 more
>
> I want to see the "11 more" lines in the error logging. How do I view
> those?
>
> Thanks.
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
[android-beginners] Re: logcat issue
My problem itself is a apk file that is downloaded to the android file system. within the file system I think you don't need to prefix adb for any command execution. to make things more clear. My program is an apk file getting executed in android file system. all it want to do is collect all logs generated by the system for a while and dump it into a file for a later parsing outside the android file system.once i get the log dumped into a file in android filesystem, i can use the adb pull command from my work station to get this file onto a local filesystem for parsing. my problem : I use the runtime exec command to start 'logcat -d >myfile' . this will create a 0 byte myfile in the specified path. but there are no logs inside that. i tried the -f method as well which again results in the creation of a 0 byte file in th specified path. How do I get the logs dumped onto myfile. why is the above commands resulting in a 0 bye file creation always? Sudheer On Sep 9, 2:43 am, DavidN <[EMAIL PROTECTED]> wrote: > Quick and dirty approach might be to "adb logcat -d >yourLocalFile". > This will dump to stdout and then redirect to a local file. > Alternately, you might logcat -f to a file and then adb pull. > > On Sep 8, 2:12 am, sudheer <[EMAIL PROTECTED]> wrote: > > > > > Hello > > I am trying to develop an application which will try to extract the > > logs generated by system when it is executed. I try to use the exec > > command to start logcat at the start of my program and later want to > > collect the log messages generated during the application execution. > > when I tried using the command 'logcat -d -f filepath', an empty file > > is created in the specified filepath . Is there any way for me to > > redirect the logs generated by application into a file in the android > > file system? > > how should I go about this? > > > Thanks in advance, > > Sudheer- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
[android-beginners] Re: logcat issue
Quick and dirty approach might be to "adb logcat -d >yourLocalFile". This will dump to stdout and then redirect to a local file. Alternately, you might logcat -f to a file and then adb pull. On Sep 8, 2:12 am, sudheer <[EMAIL PROTECTED]> wrote: > Hello > I am trying to develop an application which will try to extract the > logs generated by system when it is executed. I try to use the exec > command to start logcat at the start of my program and later want to > collect the log messages generated during the application execution. > when I tried using the command 'logcat -d -f filepath', an empty file > is created in the specified filepath . Is there any way for me to > redirect the logs generated by application into a file in the android > file system? > how should I go about this? > > Thanks in advance, > Sudheer --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~--~~~~--~~--~--~---
