吉姆小窩

How to apply a patch made by repo diff?

2017-06-17T16:36:00.004+08:00

Source: https://groups.google.com/forum/#!topic/repo-discuss/43juvD1qGIQ

## Script to patch up diff reated by `repo diff`

if [ -z "$1" ] || [ ! -e "$1" ]; then
    echo "Usages: $0 <repo_diff_file>";
    exit 0;
fi

rm -fr _tmp_splits*
cat $1 | csplit -qf '' -b "_tmp_splits.%d.diff" - '/^project.*\/$/' '{*}'

working_dir=`pwd`

for proj_diff in `ls _tmp_splits.*.diff`
do
    chg_dir=`cat $proj_diff | grep '^project.*\/$' | cut -d " " -f 2`
    echo "FILE: $proj_diff $chg_dir"
    if [ -e $chg_dir ]; then
        ( cd $chg_dir; \
            cat $working_dir/$proj_diff | grep -v '^project.*\/$' | patch -Np1;);
    else
        echo "$0: Project directory $chg_dir don't exists.";
    fi
done

Android 調試.so庫文件

2017-06-17T16:33:00.001+08:00

資料來源: http://www.blogjava.net/anymobile/articles/314685.html

作者：徐建祥(netpirate@gmail.com)
日期：2010/03/06
網址：http://www.anymobile.org

調試步驟如下：
1/ 將異常的地址信息存到文本文件，並存放在項目根目錄；
2/ 使用panic.py解析該文件；
3/ 根據返回的信息(文件名;行號;方法名)調試程序。

以操作第三方的Touch input 輸入法為例，過程如下：

# 該輸入法的英文和手寫OK，操作中文輸入法時，出現異常，軟鍵盤消失，異常日誌如下
02-05 06:41:19.834 D/dalvikvm( 751): Trying to load lib /system/lib/libimezi.so 0x43e2a788
02-05 06:41:19.874 D/dalvikvm( 751): Added shared lib /system/lib/libimezi.so 0x43e2a788
02-05 06:41:20.035 I/DEBUG   ( 551): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-05 06:41:20.035 I/DEBUG   ( 551): Build fingerprint: 'unknown'
02-05 06:41:20.035 I/DEBUG   ( 551): pid: 751, tid: 751 >>> com.htc.android.cime <<<
02-05 06:41:20.045 I/DEBUG   ( 551): signal 11 (SIGSEGV), fault addr 00000003
02-05 06:41:20.045 I/DEBUG   ( 551): r0 00000000 r1 00000000 r2 807248ec r3 807248ec
02-05 06:41:20.055 I/DEBUG   ( 551): r4 00252d80 r5 00000004 r6 00000001 r7 00000000
02-05 06:41:20.055 I/DEBUG   ( 551): r8 beff8550 r9 41459d28 10 41459d18 fp 00000000
02-05 06:41:20.055 I/DEBUG   ( 551): ip 8072430c sp beff84f0 lr 80716b4f pc 80717bce cpsr 60000030
02-05 06:41:20.135 I/DEBUG   ( 551):          #00 pc 00017bce /system/lib/libimezi.so
02-05 06:41:20.135 I/DEBUG   ( 551):          #01 pc 00010f80 /system/lib/libimezi.so
02-05 06:41:20.145 I/DEBUG   ( 551): stack:
02-05 06:41:20.155 I/DEBUG   ( 551):     beff84b0 ad083e10
02-05 06:41:20.155 I/DEBUG   ( 551):     beff84b4 ad05d44f /system/lib/libdvm.so
02-05 06:41:20.155 I/DEBUG   ( 551):     beff84b8 ad06b8a0 /system/lib/libdvm.so
02-05 06:41:20.155 I/DEBUG   ( 551):     beff84bc ad083e10
02-05 06:41:20.167 I/DEBUG   ( 551):     beff84c0 43e2aa90
02-05 06:41:20.175 I/DEBUG   ( 551):     beff84c4 00000003
02-05 06:41:20.175 I/DEBUG   ( 551):     beff84c8 00000014
02-05 06:41:20.185 I/DEBUG   ( 551):     beff84cc 80716b4f /system/lib/libimezi.so

# 保存異常日誌，存為文件: 20100205_ime.txt
02-05 06:41:20.045 I/DEBUG   ( 551): r0 00000000 r1 00000000 r2 807248ec r3 807248ec
02-05 06:41:20.055 I/DEBUG   ( 551): r4 00252d80 r5 00000004 r6 00000001 r7 00000000
02-05 06:41:20.055 I/DEBUG   ( 551): r8 beff8550 r9 41459d28 10 41459d18 fp 00000000
02-05 06:41:20.055 I/DEBUG   ( 551): ip 8072430c sp beff84f0 lr 80716b4f pc 80717bce cpsr 60000030
02-05 06:41:20.135 I/DEBUG   ( 551):          #00 pc 00017bce /system/lib/libimezi.so
02-05 06:41:20.135 I/DEBUG   ( 551):          #01 pc 00010f80 /system/lib/libimezi.so

# 執行腳本
xujianxiang@wingdroid-clone:~/workspace/xujx/wing15$ ./panic.py 20100205_ime.txt
read file ok
/home/xujianxiang/workspace/xujx/wing15/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-addr2line: '/home/xujianxiang/workspace/xujx/wing15/out/target/product/generic/symbols/system/lib/libimezi.so': No such file
Traceback (most recent call last):
File "./panic.py", line 69, in <module>
    print "%-30s%s" % (list[1],list[0])
IndexError: list index out of range

# 沒找到庫文件，因為這個文件是第三方的，只存放在/out/target/product/generic/system/lib /libimezi.so，拷貝一份存到/out/target/product/generic/symbols/system/lib /libimezi.so，再次執行腳本
xujianxiang@wingdroid-clone:~/workspace/xujx/wing15$ ./panic.py 20100205_ime.txt
read file ok
zi81keyd.c:0                  Zi8GetTableData
zi81keyd.c:0                  Zi8InitializeDynamic

# 成功解析異常，沒有zi8庫文件所致，更新如下庫文件，輸入法支持中文拼音。
/system/lib/zi/Zi8DatPYP_CN.z8d
/system/lib/zi/Zi8DatPYS_CN.z8d
/system/lib/zi/Zi8DatZHA_CN.z8d
/system/lib/zi/Zi8DatZHA_HK.z8d
/system/lib/zi/Zi8DatZHA_TW.z8d
/system/lib/zi/Zi8DatZYP_TW.z8d
/system/lib/zi/Zi8DatZYS_TW.z8d

附 panic.py：

#!/usr/bin/python
# stack symbol parser

import os
import string
import sys

#define android product name
#ANDROID_PRODUCT_NAME = 'generic'
ANDROID_PRODUCT_NAME = 'smdk6410'

ANDROID_WORKSPACE = os.getcwd()+"/"

# addr2line tool path and symbol path
addr2line_tool = ANDROID_WORKSPACE + 'prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-addr2line'
symbol_dir = ANDROID_WORKSPACE + 'out/target/product/' + ANDROID_PRODUCT_NAME +'/symbols'
symbol_bin = symbol_dir + '/system/bin/'
symbol_lib = symbol_dir + '/system/lib/'

class ReadLog:
    def __init__(self,filename):
        self.logname = filename
    def parse(self):
        f = file(self.logname,'r')
        lines = f.readlines()
        if lines != []:
            print 'read file ok'
        else:
            print 'read file failed'
        result =[]
        for line in lines:
            if line.find('stack') != -1:
                print 'stop search'
                break
            elif line.find('system') != -1:
                #print 'find one item' + line
                result.append(line)
        return result

class ParseContent:
    def __init__(self,addr,lib):
            self.address = addr # pc address
            self.exename = lib  # executable or shared library
    def addr2line(self):
        cmd = addr2line_tool + " -C -f -s -e " + symbol_dir + self.exename + " " + self.address
        #print cmd
        stream = os.popen(cmd)
        lines = stream.readlines();
        list = map(string.strip,lines)
        return list
    
inputarg = sys.argv
if len(inputarg) < 2:
    print 'Please input panic log'
    exit()

filename = inputarg[1]
readlog = ReadLog(filename)
inputlist = readlog.parse()

for item in inputlist:
    itemsplit = item.split()
    test = ParseContent(itemsplit[-2],itemsplit[-1])
    list = test.addr2line()
    print "%-30s%s" % (list[1],list[0])

[轉] 關於refs/for/

2017-02-07T12:55:00.001+08:00

資料來源: http://lishicongli.blog.163.com/blog/static/146825902013213439500/

1. 這個不是git的規則，而是gerrit的規則，
2. Branches, remote-tracking branches, and tags等等都是對commite的引用（reference）,引用都以「refs/……」表示. 比如remote branch: origin/git_int(=refs/remotes/origin/git_int)， local tag: v2.0(=refs/tags/v2.0)， local branch: git_int(=refs/heads/git_int)…
3. 簡單點說，就是refs/for/mybranch需要經過code review之後才可以提交；refs/heads/mybranch不需要code review。

（since you want to directly push into the branch, rather than create code reviews. Pushing to refs/for/* creates code reviews which must be approved and then submitted. Pushing to refs/heads/* bypasses review entirely, and just enters the commits directly into the branch. The latter does not check committer identity, making it appropriate for importing past project history）
如果需要code review，直接push
$git push origin master
那麼就會有「! [remote rejected] master -> master (prohibited by Gerrit)」的錯誤信息
而這樣push就沒有問題，
$git push origin HEAD:refs/for/mybranch

下面一段是對「refs/for」更詳細的描述：
The documentation for Gerrit explains that you push to the "magical refs/for/'branch' ref using any Git client tool".

This image is taken from the Intro to Gerrit. When you push to Gerrit, you do git push gerrit HEAD:refs/for/. This pushes your changes to the staging area (in the diagram, "Pending Changes"). Gerrit doesn't actually have a branch called ; it lies to the git client.
Internally, Gerrit has it's own implementation for the Git and SSH stacks. This allows it to provide the "magical" refs/for/ refs.
When a push request is received to create a ref in one of these namespaces Gerrit performs its own logic to update the database, and then lies to the client about the result of the operation. A successful result causes the client to believe that Gerrit has created the ref, but in reality Gerrit hasn't created the ref at all.
After a successful patch (i.e, the patch has been pushed to Gerrit, [putting it into the "Pending Changes" staging area], reviewed, and the review has passed), Gerrit pushes the change from the "Pending Changes" into the "Authoritative Repository", calculating which branch to push it into based on the magic it did when you pushed to refs/for/. This way, successfully reviewed patches can be pulled directly from the correct branches of the Authoritative Repository.

How to binarize image.

2016-11-19T14:35:00.000+08:00

* Binary image has following steps:
** To convert image to gray scale.
** To check every pixel if greater than threshold, set value to maximum(255), otherwise minimum(0).

#include <cv.hpp>

using namespace cv;
#define THRESHOLD 100

int main( int argc, char** argv )
{
  Mat image;
  image = imread( "resource/lena.png", IMREAD_COLOR );
  Mat Output( image.rows, image.cols, CV_8UC3, Scalar(0, 0, 0) );
  int height = image.rows;
  int width = image.cols;

  for(int row = 0; row < height; row++) {
      for(int col = 0; col < width; col++) {
          uchar val = (image.at<Vec3b>(row, col)[0] * 0.2999 + image.at<Vec3b>(row, col)[1] * 0.587 + image.at<Vec3b>(row, col)[2] * 0.114);

          Output.at<Vec3b>(row, col)[0] = (val > THRESHOLD ? 255 : 0);
          Output.at<Vec3b>(row, col)[1] = (val > THRESHOLD ? 255 : 0);
          Output.at<Vec3b>(row, col)[2] = (val > THRESHOLD ? 255 : 0);
      }
  }

  namedWindow("out", WINDOW_NORMAL);
  imshow("out", Output);

  waitKey(0);

  return 0;
}

Result:

How to convert grayscale image.

2016-11-18T01:54:00.000+08:00

#include <cv.hpp>

using namespace cv;

int main( int argc, char** argv )
{
  Mat image;
  image = imread( "resource/lena.png", IMREAD_COLOR );
  Mat Output( image.rows, image.cols, CV_8UC3, Scalar(0, 0, 0) );
  int height = image.rows;
  int width = image.cols;

  for(int row = 0; row < height; row++) {
      for(int col = 0; col < width; col++) {
          uchar val = (image.at<Vec3b>(row, col)[0] * 0.2999 + image.at<Vec3b>(row, col)[1] * 0.587 + image.at<Vec3b>(row, col)[2] * 0.114);
          Output.at<Vec3b>(row, col)[0] = val;
          Output.at<Vec3b>(row, col)[1] = val;
          Output.at<Vec3b>(row, col)[2] = val;
      }
  }

  namedWindow("out", WINDOW_NORMAL);
  imshow("out", Output);

  waitKey(0);

  return 0;
}

Result:

To get RGB channel and output.

2016-11-17T00:09:00.002+08:00

#include <cv.hpp>

using namespace cv;

int main( int argc, char** argv )
{
  Mat image;
  image = imread( "resource/lena.png", IMREAD_COLOR );
  Mat OutputR( image.rows, image.cols, CV_8UC3, Scalar(0, 0, 0) );
  Mat OutputG( image.rows, image.cols, CV_8UC3, Scalar(0, 0, 0) );
  Mat OutputB( image.rows, image.cols, CV_8UC3, Scalar(0, 0, 0) );
  int height = image.rows;
  int width = image.cols;

  for(int row = 0; row < height; row++) {
   for(int col = 0; col < width; col++) {

    OutputB.at<Vec3b>(row, col)[0] = image.at<Vec3b>(row, col)[0];
    OutputB.at<Vec3b>(row, col)[1] = 0;
    OutputB.at<Vec3b>(row, col)[2] = 0;
    OutputG.at<Vec3b>(row, col)[0] = 0;
    OutputG.at<Vec3b>(row, col)[1] = image.at<Vec3b>(row, col)[1];
    OutputG.at<Vec3b>(row, col)[2] = 0;
    OutputR.at<Vec3b>(row, col)[0] = 0;
    OutputR.at<Vec3b>(row, col)[1] = 0;
    OutputR.at<Vec3b>(row, col)[2] = image.at<Vec3b>(row, col)[2];
   }
  }

  namedWindow("outr", WINDOW_NORMAL);
  imshow("outr", OutputR);

  namedWindow("outg", WINDOW_NORMAL);
  imshow("outg", OutputG);

  namedWindow("outb", WINDOW_NORMAL);
  imshow("outb", OutputB);

  waitKey(0);

  return 0;
}

Results:

Using opencv to inverse Image.

2016-11-17T00:09:00.001+08:00

#include <cv.hpp>

using namespace cv;

int main( int argc, char** argv )
{
  Mat image;
  int height, width;
  // load lena picture and convert to grayscale
  image = imread("resource/lena.png", IMREAD_GRAYSCALE);
  // store height and width
  height = image.rows;
  width = image.cols;
  // show image
  imshow("lena1", image);
  // inverse image
  for(int i = 0; i < height; i++) {
      for(int j = 0; j < width; j++) {
          image.at<uchar>(i, j) = 255 - image.at<uchar>(i,j);
      }
  }
  // show image again to compare
  imshow("lena2", image);

  waitKey(0);

  return 0;
}

Result:

Eclipse mars.2 opencv configuration for mac

2016-11-17T00:09:00.000+08:00

How to configure opencv on eclipse mars.2 Release(4.5.2).
You have to install opencv3 by issue command "brew install opencv3"
* Elipse->Projects(right click)->Properties->C/C++ General->Paths and Symbols->Includes->GNU C++ -> Add
** /usr/local/Cellar/opencv3/3.1.0_2/include/opencv
** /usr/local/Cellar/opencv3/3.1.0_2/include

* Elipse->Projects(right click)->Properties->C/C++ General->Paths and Symbols->Libraries -> Add
** opencv_core (required)
** opencv_imgproc (required)
** opencv_highgui (required)
** opencv_imgcodecs (required)
** opencv_flann
** opencv_video
** opencv_features2d
** opencv_calib3d
** opencv_ml

* Elipse->Projects(right click)->Properties->C/C++ General->Paths and Symbols->Library Paths->Add
** /usr/local/Cellar/opencv3/3.1.0_2/lib

如何在 Android 各 level ( 包含 user space 與 kernel space ) 使用dump call stack的方法

2015-06-27T02:27:00.000+08:00

資料來源: 如何在 Android 各 level ( 包含 user space 與 kernel space ) 使用dump call stack的方法

dump call stack

[文章重點]

了解 Android 各 level ( UI, framework 與 HAL) 與 kernel 間, 如何印出 call stack, 方便追 code 與 debug

[文章目錄]

kernel call stack
Android Java layer
Android framework ( written by c++)
Android HAL ( written by c )
Call Stack 沒有出現 function name

kernel call stack

如果想知道call stack,也就是說, 我們想知道是誰call到func_foo(). 此時,我們可以利用 dump_stack(),放在你想dump back trace的地方就OK囉.

void func_foo(void){

  int a=3;
  ...

  dump_stack();

  ...

}

Java layer call stack

在Java檔案, 可以使用下述方法得到dump call stack

public void foo(boolean state, int flags) {
...
Log.d(TAG,"xxxx", new Throwable());
...
}

C++ layer call stack

在C/C++ 檔案, Android 已經有寫了frameworks/native/libs/utils/CallStack.cpp 供我們使用

#include <utils/CallStack.h>
...
void foo(void) {
...
   android::CallStack stack;
   stack.update();
   stack.dump("XXX");

...
}

如果你所使用是Android 4.4 之後

請改用

#include <utils/CallStack.h>
...
void foo(void) {
...
   android::CallStack stack;
   stack.update( );
   stack.log("XXX");

...
}

在Android.mk 記得要加

LOCAL_SHARED_LIBRARIES += libutils

C layer call stack

由於C去call C++需要做一些宣告, 所以將它獨立出來方便使用(dump_stack.cpp與 dump_stack.h)

dump_stack.h

#ifdef __cplusplus
extern "C" {
#endif

void dump_stack_android(void);

#ifdef __cplusplus
}
#endif

dump_stack.cpp

#include "dump_stack.h"
#include <utils/CallStack.h>

using namespace android;
extern "C"{
void dump_stack_android(void)
{
CallStack stack;
stack.update();
stack.dump("XXX");
}
}

如果你所使用是Android 4.4 之後

請改用

#include "dump_stack.h"
#include <utils/CallStack.h>

using namespace android;
extern "C"{
void dump_stack_android(void)
{
CallStack stack;
stack.update();
stack.log("XXX");
}
}

同樣地, Android.mk也需要修改

LOCAL_SRC_FILES := \
…... \
dump_stack.cpp

LOCAL_SHARED_LIBRARIES += libutils

接下來在C file中要使用時只要

extern void dump_stack_android();

void function_a()
{
…
dump_stack_android();
…
}

[ Call Stack 沒有出現 function name]
有時我們會發現在C++ 或 C 語言中使用 CallStack , 在 call dump 中並沒有出現 function name

D/XXX ( 147): #00 pc 00001b90 /system/lib/hw/audio.primary.mrvl.so (dump_stack_android+19)

D/XXX ( 147): #01 pc 00004b56 /system/lib/hw/audio.primary.mrvl.so

D/XXX ( 147): #02 pc 0001f828 /system/lib/libaudioflinger.so

D/XXX ( 147): #03 pc 00019138 /system/lib/libaudioflinger.so

D/XXX ( 147): #04 pc 00023bb6 /system/lib/libaudioflinger.so

D/XXX ( 147): #05 pc 0000e9fe /system/lib/libutils.so (android::Thread::_threadLoop(void*)+213)

D/XXX ( 147): #06 pc 0000e530 /system/lib/libutils.so

D/XXX ( 147): #07 pc 0000d208 /system/lib/libc.so (__thread_entry+72)

D/XXX ( 147): #08 pc 0000d3a4 /system/lib/libc.so (pthread_create+240)

我們追一下 CallStack 是如何被實作
先回顧一下 CallStack 是如何被使用 (以 Android 4.4 為例)

 CallStack stack;  
 stack.update();  
 stack.log();

先看一下 update( ) function 的定義 ( it is under system/core/include/utils/CallStack.h)

   // Immediately collect the stack traces for the specified thread.  
   void update(int32_t ignoreDepth=1, int32_t maxDepth=MAX_DEPTH, pid_t tid=CURRENT_THREAD);

所以透過 update( ) function, 我們可以設定想看哪一個 thread 並 dump 出多少層的 call stack, 如果都沒寫, 就是以當前的 thread 去做 call stack dump, update( ) function 會將實際可以 dump 多少的 frame 給抓出來, 其中 frame 的數量記錄在 mCount 變數, 各 frame 的資訊則記錄在 mStack[ ] 裡面, 接下來再透過 log( ) function 把 call stack 裡的 program counter 所記載的記憶體位址去把相對應的 function name 給解析出來.

 log( )  
 |--> print( )  
    |--> get_backtrace_symbols( )

看一下 get_backtrace_symbols( ) 在做些什麼

void get_backtrace_symbols(const backtrace_frame_t* backtrace, size_t frames,

backtrace_symbol_t* backtrace_symbols) {

...

for (size_t i = 0; i < frames; i++) {

...

Dl_info info;

if (dladdr((const void*)frame->absolute_pc, &info) && info.dli_sname) {

symbol->relative_symbol_addr = (uintptr_t)info.dli_saddr

- (uintptr_t)info.dli_fbase;

symbol->symbol_name = strdup(info.dli_sname);

symbol->demangled_name =
demangle_symbol_name(symbol->symbol_name);

}

...

}

release_my_map_info_list(milist);

}

這是因為它是使用 dladdr() 去讀取該share lib的 dynamic symbol 而獲取 function name

(http://stackoverflow.com/questions/11731229/dladdr-doesnt-return-the-function-name )

但是如果該 function 是宣告成 static, 該 function name 就不會出現在 dynamic symbol 裡 (你可以使用 arm-linux-androideabi-nm -D xxxx.so | grep the_function_name , 如果沒有出現, 就表示該 funciton name 並不在 dynamic symbol 裡), 遇到這情況就只好使用 add2line 指令去讀 out folder 下的 symbol 了, 各位可以參考我另一篇文章 http://janbarry0914.blogspot.tw/2011/07/android-crash-tombstone.html . 感謝.

當Android crash 該如何有效利用tombstone

2015-06-23T10:21:00.000+08:00

資料來: 當Android crash 該如何有效利用tombstone

當Android發生crash時會產生一個類似core dump的檔案在 /data/tombstones/tombstone_XX where XX is a number increased by one with each crash. 我們要如何使用該檔案呢?

tombstones_XX 檔案內容如下, 我們可以利用addr2line將pc所指的位置的function name給找出來

pid: 153, tid: 161 >>> system_server <<<

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 43bf3000

r0 003dc4a0 r1 43bf3000 r2 00000400 r3 00000000

r4 002cbc98 r5 002cbc98 r6 00000000 r7 00000000

r8 00000001 r9 00000140 10 00000019 fp 00301e04

ip 8090a1e0 sp 43f1eb68 lr 80c92cbb pc afd0cdfc cpsr 20000010

d0 003b3a700033c9f8 d1 00301280002eb23b

d2 000000000000003b d3 0000000000000000

d4 43bbc00043bb8000 d5 43d4800043bb8000

d6 3f80000000000000 d7 000001e03f000000

d8 0000000000000000 d9 0000000000000000

d10 0000000000000000 d11 0000000000000000

d12 0000000000000000 d13 0000000000000000

d14 0000000000000000 d15 0000000000000000

d16 3effff003effff00 d17 3f80000041808889

d18 3f80000041c4cccd d19 0701070100700798

d20 0000000000000c27 d21 0000043f00890000

d22 0000000000000000 d23 0000000000000008

d24 3fc74721cad6b0ed d25 3fc39a09d078c69f

d26 0000000000000000 d27 0000000000000000

d28 0000000000000000 d29 0000000000000000

d30 0000000000000000 d31 0000000000000000

scr 20000010

#00 pc 0000cdfc /system/lib/libc.so

#01 pc 00092cb8 /system/lib/egl/libGLESv2_adreno200.so

#02 pc 00093814 /system/lib/egl/libGLESv2_adreno200.so

#03 pc 00093890 /system/lib/egl/libGLESv2_adreno200.so

#04 pc 000938bc /system/lib/egl/libGLESv2_adreno200.so

#05 pc 00095cce /system/lib/egl/libGLESv2_adreno200.so

#06 pc 0006526a /system/lib/egl/libGLESv2_adreno200.so

#07 pc 000655cc /system/lib/egl/libGLESv2_adreno200.so

#08 pc 000188c4 /system/lib/egl/libGLESv1_CM_adreno200.so

#09 pc 000265ca /system/lib/libsurfaceflinger.so

#10 pc 0001b04c /system/lib/libsurfaceflinger.so

#11 pc 0001bda8 /system/lib/libsurfaceflinger.so

#12 pc 0001bf52 /system/lib/libsurfaceflinger.so

#13 pc 00020f3c /system/lib/libsurfaceflinger.so

#14 pc 00023df6 /system/lib/libsurfaceflinger.so

#15 pc 000259de /system/lib/libsurfaceflinger.so

#16 pc 0001c52c /system/lib/libutils.so

#17 pc 0001ca8a /system/lib/libutils.so

#18 pc 00011bc4 /system/lib/libc.so

#19 pc 00011790 /system/lib/libc.so

1. Android 產生出來的還沒進行strip的執行檔或shared libraries 是放在$android_root/out/target/product/YOUR_PRODUCT_NAME/symbols/system/bin 與 $android_root/out/target/product/YOUR_PRODUCT_NAME/symbols/system/lib目錄下

2. Android所使用的toolchain是放在$android_root/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ 下面

3. 假設我們要看 #09 pc 000265ca /system/lib/libsurfaceflinger.so 是 call 到哪一個function

(假設tombstone_XX 是在 $android_root 目錄下)

$ ./prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-addr2line -f -e ./out/target/product/YOUR_PRODUCT_NAME/symbols/system/lib/libsurfaceflinger.so 0x000265ca

它會show出_ZN7android14TextureManager12initEglImageEPNS_5ImageEPvRKNS_2spINS_13GraphicBufferEEE

$android_root/frameworks/base/services/surfaceflinger/TextureManager.cpp:164 這樣的訊息

參考網站: http://crazydaks.com/debugging-in-android-with-tombstones.html

How do you read a segfault kernel log message

2015-06-01T23:23:00.000+08:00

Reference: How do you read a segfault kernel log message

This can be a very simple question, I'm am attempting to debug an application which generates the following segfault error in the kern.log

kernel: myapp[15514]: segfault at 794ef0 ip 080513b sp 794ef0 error 6 in myapp[8048000+24000]

Here are my questions:

Is there any documentation as to what are the diff error numbers on segfault, in this instance it is error 6, but i've seen error 4, 5

What is the meaning of the information at bf794ef0 ip 0805130b sp bf794ef0 and myapp[8048000+24000]?

So far i was able to compile with symbols, and when i do a x 0x8048000+24000 it returns a symbol, is that the correct way of doing it? My assumptions thus far are the following:

sp = stack pointer?
ip = instruction pointer
at = ????
myapp[8048000+24000] = address of symbol?

Based on my limited knowledge, your assumptions are correct.

sp = stack pointer
ip = instruction pointer
myapp[8048000+24000] = address

If I were debugging the problem I would modify the code to produce a core dump or log a stack backtrace on the crash. You might also run the program under (or attach) GDB.

The error code is just the architectural error code for page faults and seems to be architecture specific. They are often documented in arch/*/mm/fault.c in the kernel source. My copy of Linux/arch/i386/mm/fault.c has the following definition for error_code:

bit 0 == 0 means no page found, 1 means protection fault
bit 1 == 0 means read, 1 means write
bit 2 == 0 means kernel, 1 means user-mode

My copy of Linux/arch/x86_64/mm/fault.c adds the following:

bit 3 == 1 means fault was an instruction fetch

Answer:

When the report points to a program, not a shared library

Run addr2line -e myapp 080513b (and repeat for the other instruction pointer values given) to see where the error is happening. Better, get a debug-instrumented build, and reproduce the problem under a debugger such as gdb.
If it's a shared library

In the libfoo.so[NNNNNN+YYYY] part, the NNNNNN is where the library was loaded. Subtract this from the instruction pointer (ip) and you'll get the offset into the .so of the offending instruction. Then you can use objdump -DCgl libfoo.so and search for the instruction at that offset. You should easily be able to figure out which function it is from the asm labels. If the .so doesn't have optimizations you can also try using addr2line -e libfoo.so .
What the error means

Here's the breakdown of the fields:

address - the location in memory the code is trying to access (it's likely that 10 and 11 are offsets from a pointer we expect to be set to a valid value but which is instead pointing to 0)
ip - instruction pointer, ie. where the code which is trying to do this lives
sp - stack pointer
error - Architecture-specific flags; see arch/*/mm/fault.c for your platform.

Implement Camera (former: CCCamera) v2 in cocos2d-x v3.3

2015-05-23T02:44:00.003+08:00

Reference: Implement Camera (former: CCCamera) v2 in cocos2d-x v3.3

we want to port camera code from cocos2d-x version 2 to version 3.3 with the goal to imitate the behaviour of a CCCamera in cocos2d-x version 2 exactly.

You can assume that values for "eye" and "up" are calculated correctly.

Old code operating on CCCamera:

camera->setEyeXYZ(eye.x, eye.y, 0);
camera->setCenterXYZ(eye.x, eye.y, -1);
camera->setUpXYZ(up.x, up.y, 0);

New code operating on Camera:

camera->setPosition3D(Vec3(eye.x, eye.y, 0.0f));
camera->lookAt(Vec3(eye.x, eye.y, -1), Vec3(up.x, up.y, 0.0f));

The setPosition3D part works fine and this is also a good indicator that I've set up the camera correctly in terms of setCameraFlag and Mask, correct layers, etc. but for some reason the tilting (modification of the up vector) doesn't work fine, it's kind of hard to describe, but it doesn't seem that the view matrix is calculated as intended.

The examples only contain code with fixed up vectors, e.g. Vec3(0, 1, 0), but I really need a dynamic one.

Thanks in advance, Chris

Cocos2d-x v3 C++ Tutorial 36 - Touch Began Using onTouchBegan - 學習筆記

2015-05-23T02:37:00.000+08:00

資料來源: Cocos2d-x v3 C++ Tutorial 36 - Touch Began Using onTouchBegan

* 如何在 Cocos2d-x v3.6 C++ 收 onTouchBegan 事件
** 增加下列代碼在 cpp init 函數

auto listener = EventListenerTouchOneByOne::create();
listener->setSwallowTouches(true);
listener->onTouchBegan = CC_CALLBACK_2(HelloWorld::onTouchBegan, this);
_eventDispatcher->addEventListenerWithSceneGraphPriority(listener, this);

** 增加下列代碼(函數)在 cpp 檔

bool HelloWorld::onTouchBegan(cocos2d::Touch *touch, cocos2d::Event *event)
{
    CCLOG("onTouchBegan x = %f, y = %f", touch->getLocation().x, touch->getLocation().y);
    return true;
}

** 增加下列代碼(函數宣告) 在 header 檔

bool onTouchBegan(cocos2d::Touch *touch, cocos2d::Event *event);

cocos2d android Java 游戲開發基礎 10 - 時間調度學習視頻筆記

2015-05-17T19:43:00.000+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* 為什麼需要時間調度
* schedule() 方法的使用
    this.schedule("func", 1)
// delta 往往用來表示增量，在當前的例子當中，該變量的值為上次調用 fun 函數與這次調用 fun 函數之間的時間差
public void fun(float delta) {
    System.out.println("調用的 fun 函數, delta 的值為 " + delta);
}

* delta 參數的作用
** delta 為上次和這次執行函數 func 的時間差
* unschedule() 方法的使用
    this.unschedule("func")
* 總結

cocos2d android Java 游戲開發基礎 9 - 觸屏事件學習視頻筆記

2015-05-16T17:16:00.002+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* Android 平台觸摸事件回顧
* 設置圖層接收觸摸事件
** this.setIsTouchEnabled(true)
* 觸摸回調函數
** ccTouchesBegan(), ccTouchesMoved(), ccTouchesEnded()
* 觸摸點坐標轉換
** CCDirector.sharedDirector().convertToGL(CGPoint)
* 總結

cocos2d android Java 游戲開發基礎 8 - CCAction 初步 (四)學習視頻筆記

2015-05-16T02:14:00.000+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* CCFadeIn 與 CCFadeOut
    CCFadeIn ccFadeIn = CCFadeIn.action(3);
    player.runAction(ccFadeIn);
    CCFadeOut ccFadeOut = CCFadeOut.action(3);
    player.runAction(ccFadeOut);

* CCTintTo 與 CCTintBy
    ccColor3B color3b = ccColor3B.ccc3(0, 0, 255);
    CCTintTo ccTintTo = CCTintTo.action(3, color3b);
    player.runAction(ccTintTo);

    ccColor3B color3b = ccColor3B.ccc3(-120, -255, -120);
    CCTintBy ccTintBy = CCTintBy.action(3, color3b);
    player.runAction(ccTintBy);

* CCRepeat
CGPoint cgPoint = CGPoint.ccp(100, 300);
    CGPoint targetPoint = CGPoint.ccp(400, 300);
    CCMoveTo moveTo1 = CCMoveTo.action(2, targetPoint);
    CCMoveTo moveTo2 = CCMoveTo.action(2, cgPoint);
    CCSequence ccSequence = CCSequence.actions(moveTo1, moveTo2);

    CCRepeat ccRepeat = CCRepeat.action(ccSequence, 3);
    player.runAction(ccRepeat);

* CCRepeatForever
    CCRepeatForever ccRepeatForever = CCRepeatForever.action(ccSequence);
    player.runAction(ccRepeatForever);

Priority inversion learning note

2015-05-14T20:25:00.000+08:00

* Bounded priority inversion

* Unbounded priority inversion

How to solve
* Priority inheritance protocol
Raised the low priority task which locked shared resource to high priority to finish task and release shared resource soon.

* Priority ceiling protocol
** OCPP: Original Ceiling Priority Protocol
Raised the task (locked resource) priority to high priority when another task tries to acquire shared resource.

** ICPP: Immediate Ceiling Priority Protocol
Raised the task priority to high priority when it acquires resource.

Reference:
http://en.wikipedia.org/wiki/Priority_inheritance
http://en.wikipedia.org/wiki/Priority_ceiling_protocol
http://blog.linux.org.tw/~jserv/archives/001299.html
http://oss.org.cn/ossdocs/rt_embed/rt/priority.html
http://wen00072-blog.logdown.com/posts/183461-note-priority-inversion-on-mars
http://www.embedded.com/design/configurable-systems/4024970/How-to-use-priority-inheritance

cocos2d android Java 游戲開發基礎 7 - CCAction 初步 (三) 學習視頻筆記

2015-05-14T20:24:00.000+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* CCSequence 的使用方法
** 一連串的動作依序執行
    CGPoint targetPoint = CGPoint.ccp(500, 500);
    CCMoveTo moveTo = CCMoveTo.action(5, targetPoint);
    CCRotateTo rotateTo = CCRotateTo.action(5, 180);
    CCScaleTo scaleTo = CCScaleTo.action(2, 2);
    CCSequence ccSequence = CCSequence.actions(moveTo, rotateTo, scaleTo);
player.runAction(ccSequence);

* CCSpawn 的使用方法
** 一連串的動作同時間執行
    CCSpawn ccSpawn = CCSpawn.actions(moveTo, rotateTo, scaleTo);
    player.runAction(ccSpawn);

* CCCallfuncN 的使用方法
** 用於一個動作作完後所要執行的動作
    CCCallFuncN funcN = CCCallFuncN.action(this, "onActionFinished");
player.runAction(funcN);

* CCFollow 的使用方法
    CCFollow ccFollow = CCFollow.action(followedNode, rect);
    player.runAction(ccFollow);
* 總結

cocos2d android Java 游戲開發基礎 6 - CCAction 初步 (二) 學習視頻筆記

2015-05-14T20:11:00.000+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* 什麼是向量
* 基于向量的計算
** 向量的加減法
    CGPoint deltaPoint = CGPoint.ccp(0, 200);
    CGPoint targetPoint = CGPoint.ccpAdd(cgPoint, deltaPoint);
CGPoint subPoint = CGPoint.ccp(200, 300);
    CGPoint tgPoint = CGPoint.ccpSub(targetPoint, subPoint);
** 向量的乘除法
    CGPoint newPoint = CGPoint.ccpMult(tgPoint, 2);
** 計算單位向量
* 使用 CGPoint 對象代表向量
    CGPoint anotherPoint = CGPoint.ccpNormalize(tgPoint);
* 基于向量的運算
* CCMoveBy 與 CCJumpBy
    CGPoint onePoint = CGPoint.ccp(500, 300);
    CCMoveBy moveBy = CCMoveBy.action(5, onePoint);

    CGPoint jumpPoint = CGPoint.ccp(300, 100);
    CCJumpBy jumpBy = CCJumpBy.action(5, deltaPoint, 500, 5);
* 總結

cocos2d android Java 游戲開發基礎 5 - CCAction 初步 (一) 學習視頻筆記

2015-05-12T20:13:00.001+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* 動作類的基本概念
** 動作類對象通常不會單獨存在
** 動作類對象需要作用在精靈，圖層等對象上才能發揮作用
** 動作類包含有很多種類型，例如位移，縮放和旋轉等

* 動作類的分類方法
** CCAction -- CCFiniteTimeAction -- CCActionInstant
**           |                     |- CCActionInterval
**         |- CCFollow
**         |- CCSpeed

* 基礎瞬時動作使用方法 - CCActionInstant
**   動作      描述
** CCFlipX X軸鏡像翻轉
** CCFlipY Y軸鏡像翻轉
** CCHide   隱藏
** CCShow   顯示

* 基礎延時動作使用方法 - CCActionInterval
**   動作        描述
** CCMoveTo    移動至目標
** CCRotateTo 旋轉至指定的角度
** CCScaleTo   縮放至指定的倍數
** CCBlink     閃爍

* 總結

cocos2d android Java 游戲開發基礎 4 - 精靈初體驗學習視頻筆記

2015-05-12T20:12:00.003+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

* 什麼是精靈
** 精靈是游戲中的一個元素，通常用於代表畫面當中的一個事物，例如主人公，NPC 和背景元素等等
** 一個精靈對象通常都與一張圖片關聯
** 精靈對象通常可以通過運行動作對象 (CCAction) 來產生動畫效果

** 如何生成一個精靈對象
    CCSprite player;
    player = CCSprite.sprite("player.png");

** 讓精靈對象添加至布景層當中
    this.addChild(player);
** 運行動作對象 (CCAction)
    CGPoint target = CGPoint.ccp(400, 100); // 設定目標座標
    CCJumpTo jumpTo = CCJumpTo.action(3, target, 200, 3); //設定 JumpTo(CCAction) 參數說明 (執行3秒, 跳到 target 座標, 跳動高度, 跳動次數)
    player.runAction(jumpTo);

** 總結

cocos2d android Java 遊戲開發基礎 3 - Cocos2d 創世紀學習視頻筆記

2015-05-12T20:12:00.001+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

*創建第一個 Cocos2d 應用程序
** 創建一個 Android 應用程序
** 生成一個 SurfaceView 對象，作為 Activity 當中所顯示的內容
    view = new CCGLSurfaceView(this);
** 得到 CCDirector 對象，並通過該對象設置應用程序的各種屬性
    CCDirector director = CCDirector.sharedDirector();

** 設置應用程序基本屬性
*** 用於設置應用程序所使用的 GL 視圖對象
    director.attachInView(mGLSurfaceView)
*** 用於設置應用程序的方向
director.setDeviceOrientation(CCDirector.kCCDeviceOrientationLandscapeLeft);
*** 設置應用程序是否需要顯示應用程序的 FPS 值
    director.setDisplayFPS(true);
*** 設置每幀所需要的時間
    director.setAnimationInterval(1.0f / 30)

** 生成場景與布景層
*** 創建一個布景層類，繼承 CCLayer
    public class GameLayer extends CCLayer {
public GameLayer() {
        }
    }
*** 調用 CCScene 類的 node() 方法生成場景對象
CCScene scene = CCScene.node();
*** 生成布景層對象，並添加至場景對象當中
    GameLayer gameLayer = new GameLayer();
    scene.addChild(gameLayer);
*** 執行場景對象
    director.runWithScene(scene);

** 運行 Cocos2d 應用程序
** 總結

cocos2d android Java 遊戲開發基礎 2 - 安裝學習視頻筆記

2015-05-12T20:11:00.001+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

抓包來安裝：到 github 找 cocos2d android, 抓 ZhouWeikuan 的 zip 檔下來套用到 Android 已存在項目.
修改 library 和把重覆的類改名後，即可編譯。

cocos2d android Java 遊戲開發基礎1 - 介紹學習視頻筆記

2015-05-12T00:04:00.002+08:00

資料來源: 千鋒獨家出品《Android遊戲開發基礎視頻教程》http://www.mobiletrain.org/about/news/android_video3.html

導演－－場景1－－布景層1 -- 精靈1
         |     | |
         | | |-- 精靈2
         | |-- 布景層2   |-- 精靈3
         |-- 場景2       |-- 布景層3   |-- 精靈4
                                                  |
                                                  - 精靈5

CCDirector: 導演類
CCScene: 場景類
CCLayer: 布景層
CCSprite: 精靈

使用 xmllint 處理/驗證 xml

2014-12-29T15:35:00.000+08:00

資料來源: http://blog.csdn.net/qmhball/article/details/8955588

xmllint是一個很方便的處理及驗證xml的工具，linux下只要安裝libxml2就可以使用這個命令，下面整理一些常用功能

1. --format

此參數用於格式化xml，使其具有良好的可讀性。

假設有xml（person.xml）內容如下:

<person><name>ball</name><age>30</age><sex>male</sex></person>

執行：

xmllint --format person.xml

得到易讀的xml

<person>  
      <name>ball</name>  
      <age>30</age>  
      <sex>male</sex>  
</person>

2. --noblanks

與--format相反，有時為了節省傳輸量，我們希望去掉xml中的空白，這時我們可以使用--noblanks命令。

假設xml（person.xml）內容如下

<?xml version="1.0"?>  
<person>  
  <name>ball</name>  
  <age>30</age>  
  <sex>male</sex>  
</person>

執行：

xmllint --noblanks person.xml

得到去掉空白後的xml

ball30male

3.--schema

使用scheam驗證xml文件的正確性（瞭解schema的知識請猛擊這裡）

假設有xml文件（person.xml）和scheam文件（person.xsd）文件，內容分別如下

person.xml

<?xml version="1.0"?>  
<person>  
  <name>ball</name>  
  <age>30</age>  
  <sex>male</sex> 
</person>

person.xsd

<?xml version="1.0"?>  
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">  
  <xs:element name="name" type="xs:string"/>  
  <xs:element name="age" type="xs:integer"/>  
  <xs:element name="sex">  
    <xs:simpleType>  
      <xs:restriction base="xs:string">  
        <xs:enumeration value="male"/>  
        <xs:enumeration value="female"/>  
      </xs:restriction>  
    </xs:simpleType>  
  </xs:element>  
  <xs:element name="person">  
    <xs:complexType>  
      <xs:all>  
        <xs:element ref="name"/>  
        <xs:element ref="age"/>  
        <xs:element ref="sex"/>  
      </xs:all>  
    </xs:complexType>  
  </xs:element>  
</xs:schema>

執行:

xmllint --schema person.xsd person.xml

得到

  
  ball  
  30  
  male  
  
person.xml validates

注意，默認情況下，驗證後會輸出驗證的文件內容，可以使用 --noout選項去掉此輸出，這樣我們可以只得到最後的驗證結果。

執行

xmllint --noout --schema person.xsd person.xml

得到

person.xml validates

下面我們改動person.xml

<?xml version="1.0"?>  
<person>  
  <name>ball</name>  
  <age>not age</age>  
  <sex>test</sex>  
</person>

顯然，這份文件age字段和sex都是不符合xsd定義的。

執行

xmllint --noout --schema person.xsd person.xml

得到：

person.xml:4: element age: Schemas validity error : Element 'age': 'not age' is not a valid value of the atomic type 'xs:integer'.  
person.xml:5: element sex: Schemas validity error : Element 'sex': [facet 'enumeration'] The value 'test' is not an element of the set {'male', 'female'}.  
person.xml:5: element sex: Schemas validity error : Element 'sex': 'test' is not a valid value of the local atomic type.  
person.xml fails to validate

good！xmllint成功的報出了錯誤！

4. 關於--schema的輸出

在講輸出之前先看下面一個場景，假如你想通過php執行xmllint然後拿到返回結果，你的代碼通常應該是這個樣子

valid.php

<?php  
$command = "xmllint --noout --schema person.xsd person.xml";  
exec($command, $output, $retval);  
//出錯時返回值不為0  
if ($retval != 0){   
        var_dump($output);      
}  
else{  
    echo "yeah!";  
}

我們保持上文中person.xml的錯誤。

執行此代碼，你會發現，你拿到的output不是錯誤，而是array(0) {}, amazing！

為什麼會這樣呢？

因為xmllint --schema，如果驗證出錯誤，錯誤信息並不是通過標準輸出（stdout）顯示的，而是通過標準錯誤（stderr）進行顯示的。

而exec的output參數拿到的，只能是標準輸出（stdout）顯示的內容。

所以，為了拿到出錯信息，我們需要將標準錯誤重定向到標準輸出，對應修改代碼：

$command = "xmllint --noout --schema person.xsd person.xml 2>&1";

再次執行valid.php，錯誤信息順利拿到！

附小問題

--noout參數關閉的是什麼輸出呢:)

吉姆小窩

How to apply a patch made by repo diff?

Android 調試.so庫文件

[轉] 關於refs/for/

How to binarize image.

How to convert grayscale image.

To get RGB channel and output.

Using opencv to inverse Image.

Eclipse mars.2 opencv configuration for mac

如何在 Android 各 level ( 包含 user space 與 kernel space ) 使用dump call stack的方法

dump call stack

[文章重點]

kernel call stack

C++ layer call stack

C layer call stack

當Android crash 該如何有效利用tombstone

How do you read a segfault kernel log message

Implement Camera (former: CCCamera) v2 in cocos2d-x v3.3

Cocos2d-x v3 C++ Tutorial 36 - Touch Began Using onTouchBegan - 學習筆記

cocos2d android Java 游戲開發基礎 10 - 時間調度 學習視頻筆記

cocos2d android Java 游戲開發基礎 9 - 觸屏事件 學習視頻筆記

cocos2d android Java 游戲開發基礎 8 - CCAction 初步 (四)學習視頻筆記

Priority inversion learning note

cocos2d android Java 游戲開發基礎 7 - CCAction 初步 (三) 學習視頻筆記

cocos2d android Java 游戲開發基礎 6 - CCAction 初步 (二) 學習視頻筆記

cocos2d android Java 游戲開發基礎 5 - CCAction 初步 (一) 學習視頻筆記

cocos2d android Java 游戲開發基礎 4 - 精靈初體驗 學習視頻筆記

cocos2d android Java 遊戲開發基礎 3 - Cocos2d 創世紀 學習視頻筆記

cocos2d android Java 遊戲開發基礎 2 - 安裝 學習視頻筆記

cocos2d android Java 遊戲開發基礎1 - 介紹 學習視頻筆記

使用 xmllint 處理/驗證 xml

cocos2d android Java 游戲開發基礎 10 - 時間調度學習視頻筆記

cocos2d android Java 游戲開發基礎 9 - 觸屏事件學習視頻筆記

cocos2d android Java 游戲開發基礎 4 - 精靈初體驗學習視頻筆記

cocos2d android Java 遊戲開發基礎 3 - Cocos2d 創世紀學習視頻筆記

cocos2d android Java 遊戲開發基礎 2 - 安裝學習視頻筆記

cocos2d android Java 遊戲開發基礎1 - 介紹學習視頻筆記