Page 1 of 1

API stack backtrace

PostPosted: Thu Jul 09, 2020 6:13 am
by ajitchavan
Hi Team,

I need to backtrace API call stack of chromium/cef to my application and vice versa.

My application is crashing and there is no way I can debug it as I do not get core dump and can not use gdb.

Is there any way I can get to see what all API's are called from my application and what all callbacks I have received.

Re: API stack backtrace

PostPosted: Thu Jul 09, 2020 6:30 am
by Czarek
You can download debug symbols from where you've obtained CEF binaries. What do you mean you cannot use gdb?

Re: API stack backtrace

PostPosted: Thu Jul 09, 2020 8:17 am
by ajitchavan
Czarek wrote:You can download debug symbols from where you've obtained CEF binaries. What do you mean you cannot use gdb?


Thank you Czarek, actually my visual studio code can not connect remotely to server to browse code so can not use it. So can not use gdb to debug code.

Re: API stack backtrace

PostPosted: Thu Jul 09, 2020 12:04 pm
by Czarek
CEF has a built-in crash reporting called Crashpad, see cef_crash_util.h.

Re: API stack backtrace

PostPosted: Fri Jul 10, 2020 4:12 am
by ajitchavan
Czarek wrote:CEF has a built-in crash reporting called Crashpad, see cef_crash_util.h.


On wiki https://bitbucket.org/chromiumembedded/ ... porting.md, I see "The crash reporting capability in CEF/Chromium is implemented using Crashpad on Windows and macOS, and Breakpad on Linux".
Our application can be used from windows, mac and linux. and we use linux to develop and build it. In that case I need to configure breakpad but not crashpad.

Please correct me if wrong.

Re: API stack backtrace

PostPosted: Fri Jul 10, 2020 4:52 am
by Czarek
Chromium documentation confirms it: https://www.chromium.org/developers/crash-reports

Re: API stack backtrace

PostPosted: Fri Jul 10, 2020 5:20 am
by ajitchavan
Czarek wrote:Chromium documentation confirms it: https://www.chromium.org/developers/crash-reports


Thank you Czarek, this documentation looks good. will follow it.