>>Is there better way than just to change the function 'write()' to
'LOGI()'???
did u meant write(fd, result.string(), result.size()) calls?
you can try printing the buffer, as it getting populated LOGE("%s", *buffer)
or try if u can print the whole result in the end, like
result.append("\0");
LOGE("%s", result.string())
Also, in general, u can add custom traces on user libraries, via below
steps..
- in source, add
#include <utils/Log.h>
#undef LOG_TAG
#define LOG_TAG "My-Module"
- Add your traces
LOGE("Print %d %s", i, *s); //LOGE - error cases, LOGD-debug,
LOGI-informational
- after bootup, run 'logcat' in shell to get the traces.
On Sun, May 16, 2010 at 10:23 PM, Changyong shin <[email protected]> wrote:
> Hello, All?
>
> Now I'm reading the sources related with Audio.
> BTW, I've found many dump methods of the Audio classes.
> And I had tried to use & dump their status of each Audio classes, just
> giving them fd 4, 5, or 6 - these fds are using by Android Logging system.
> But adb just shows me "out of memory".
> Is there better way than just to change the function 'write()' to
> 'LOGI()'???
> I'd like to see their status with other logs...
>
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<android-platform%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.
>
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
