[android-developers] There are so many Android app developers just insist the external storage access

2017-02-12 Thread Dewr
Even though Google provides ways to give and take between apps without losing the secure filesystem isolation - e.g. ACTION_GET_CONTENT and the sharing system - there are so many Android app developers who just insist the external storage access. So I would really love to see Google provide nor

[android-developers] ndk-gdb on cygwin/windowsXP won't load symbol tables.

2011-02-06 Thread Dewr
o: No such file or directory. > Error while mapping shared library sections: > libstlport.so: No such file or directory. > Error while mapping shared library sections: > libwebcore.so: No such file or directory. > Error while mapping shared library sections: > gralloc.qsd8k.so: No such

[android-developers] Re: ndk-gdb on cygwin/windowsXP won't load symbol tables.

2011-02-08 Thread Dewr
:= -g #debug > LOCAL_LDFLAGS := -Wl,-Map,xxx.map #create map file > > LOCAL_SRC_FILES := \ > android_helper.c \ > str_lib.c \ > io_lib.c \ > xxx.c \ > util.c > LOCAL_LDLIBS := -llog #logcat > > include $(BUILD_SHARED_LIBRARY) > On Mon, Feb 7, 20

[android-developers] Re: ndk-gdb on cygwin/windowsXP won't load symbol tables.

2011-02-08 Thread Dewr
at before, I have put codes above of 'include $(CLEAR_VARS)' stupidly. On Wed, Feb 9, 2011 at 11:15 AM, Dewr wrote: > I has done this job by editing Android.mk. > moving 'LOCAL_CFLAGS := -g #debug' line to below of 'LOCAL_MODULE:= > libxxx' &g

Re: [android-developers] onItemSelectedListener causes gallery to jump, stick and pop...

2011-02-17 Thread Dewr
Hi Richard. Have you solved this problem? I am getting pain from same problem. :( But I have seen an app works well smoothly. the name of it is '예스24'. On 1/13/11, Richard Schilling wrote: > I have a gallery on my screen. Works great and scrolls smoothly ... > until I set the OnItemSelectedListe

[android-developers] Re: ndk-gdb on cygwin/windowsXP won't load symbol tables.

2011-02-22 Thread Dewr
Today, I deleted this line, but ndk-gdb still does the jobs well. > LOCAL_CFLAGS := -g #debug > On Wed, Feb 9, 2011 at 12:00 PM, Dewr wrote: > at before, I have put codes above of 'include $(CLEAR_VARS)' stupidly. > > > On Wed, Feb 9, 2011 at 11:15 AM, Dewr wrote:

[android-developers] [bionic-c-lib] SIGSEGV on free()

2011-02-23 Thread Dewr
Cygwin. I am using *android.content.res.AssetFileDescriptor* to read assets in C modules. Here is the messages in ndk-gdb when the problem appears. > (gdb) c > Continuing. > > Breakpoint 2, Java_kr_co_pkbio_Unse_DangSaJuShinSal (env=0xaa50, > obj=0x4495b970) > at > C:/DEWR/Product/So

[android-developers] Re: [bionic-c-lib] SIGSEGV on free()

2011-02-23 Thread Dewr
malloc didn't return NULL. so memories maybe allocated correctly. On Thu, Feb 24, 2011 at 1:15 PM, Dewr wrote: > Hello, I am porting a C program. > > The problem I've met is SIGSEGV on free(). I can't see what's the root > cause of it. > it doesn't o

[android-developers] Re: [bionic-c-lib] SIGSEGV on free()

2011-02-24 Thread Dewr
I am controlling lifetime of AssetFileDescriptors. I don't use terminated FileDescriptors. Do I have to re-code I/O routines in Java or not to free allocated memories? On Thu, Feb 24, 2011 at 1:15 PM, Dewr wrote: > Hello, I am porting a C program. > > The problem I've met

[android-developers] Re: [bionic-c-lib] SIGSEGV on free()

2011-02-24 Thread Dewr
nction.* > if (strBuf == NULL) > buf_output[i] = NULL; > else > { > buf_output[i] = (*gEnv)->NewStringUTF(gEnv, strBuf); > *free(strBuf);* > } > } > On Thu, Feb 24, 2011 at 1:15 PM, Dewr wrote: >

[android-developers] Re: [bionic-c-lib] SIGSEGV on free()

2011-03-22 Thread Dewr
asset files directly but accessing copied ones. On Fri, Feb 25, 2011 at 1:10 PM, Dewr wrote: > it often causes SIGSEGV on third for-loop. but just a moment ago SIGSEGV on > fourth loop. > >> for ( i = 0 ; i < 4 ; i++ ) { >> sprintf (temp, &quo

Re: [android-developers] Re: SIGSEGV on free()

2011-03-23 Thread Dewr
ediately with x=NULL, > and you will probably not crash anymore. Matching your malloc()/ > free() > calls carefully and logically tends to fix such problems. > > > > > On Mar 22, 4:26 am, Dewr wrote: > > I have tested it on Galaxy S and it worked well on Galaxy S (2