What kind of debug output statement is valid in getaddrinfo.c?

by 鎹疯秴 鐜 » Fri, 20 May 2011 17:17:53 GMT


Sponsored Links
 Hi, developers:

I am currently developing an IPv6 DNS resolver on Android-x86 platform
in socket programming in C so I would like to modify some code in /
home/ubuntu/android-x86/bionic/libc/netbsd/net/getaddrinfo.c". I want
to do debugging in this file so I am trying to adding debug output
statements in this file.

I 've tried "LOGE", "printf" and "fprintf" but none of them works.
Is there anyone knows what kind of debug output statement is valid in
this file? Thank you very much!!

Best wishes,

Jiechao Wang
BUPT

-- 



Other Threads

1. Would Android Phones be equipped with WiMax chip ?

Sprint seems to be reviving its WiMax plans with Clearwire. The
article talks about PCs being shipped with WiMax.

http://www.bloomberg.com/apps/news?pid=20601087&sid=aKalOFV2vcNo&refer=home

I am wondering if Android phones would ship with WiMax as well, or
with some alternative technology like support for UMA or femtocells.
Then applications like FluidNexus could use a network even if the
voice or SMS networks were down.

--~--~---------~--~----~------------~-------~--~----~

2. how to replace core android classes - or is there a way to add -Xbootclasspath to .apk startup?

Specifically we need to replace WebView's CacheManager to fix bugs in
it and provide an alternative implementation. (This new CacheManager
would be used in open source Browser Bhoost product - see http://bhoost.com).
It should not be a security problem for Android since it would affect
the bootclasspath only for the Bhoost process.

Ideally -Xbootclasspath option should be available both through
Eclipse plugin and via command line tools. I know it is possible to
start dalvikvm and specify this option (as shown here:
http://davanum.wordpress.com/2007/12/04/command-line-java-on-dalvikvm/).
But we did not expect Judges for ADC I submission to be able to do
that. So, this is a hard requirement for Bhoost project to be able to
compete in ADC II.
--~--~---------~--~----~------------~-------~--~----~

3. Another Moseycode release

4. Taking a breather

5. Problem with the heap size

6. Mobilogger project first release

7. When will the next version of SDK be published