Languages

Menu
Sites
Language
crash debug information

Hello All,

I use SM-Z300F smartphone and develop native application using tizen SDK.

When I run my application in some cases my application is crashes due to errors, and I receive *.cs file in crash-info directory of my project.

In this file I receive some debug information (some info from logcat, call stack, threads, maps info).

Call Stack info usually is very small, like this:

Callstack Information (PID:15282)
Call Stack Count: 1
 0: gsignal + 0x34 (0xb6925b84) [/lib/libc.so.6] + 0x2bb84
End of Call Stack

 

Such information is very small and poor in order to debug problems. Where it is possible to get addition information?

For example core files like in unix systems would be useful to view the whole stack like using gdb utility.

Maybe there is some additional info in filesystem, some files, which can be read?

I need to know why my program crashes and get full info on this.

 

Responses

1 Replies
Nafisul Islam Kiron

Hello, normally we debug our app step by step using breakpoints. We observe if our expected values are achieved and mark milestones when a certain portion of code is reached. This is the most basic and effective way. Another way of tracing app is setting dlog() log with tags. They print the values from our objects and variables.

You can find all the app's behaviour in Console, Log and Call Stack tabs while debugging.