Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Mac] Crash dumps doesn't match hashes of symbol files #4450

Closed
ghostoy opened this issue Feb 24, 2016 · 4 comments
Closed

[Mac] Crash dumps doesn't match hashes of symbol files #4450

ghostoy opened this issue Feb 24, 2016 · 4 comments
Labels
Milestone

Comments

@ghostoy
Copy link
Member

ghostoy commented Feb 24, 2016

Manually triggering crashes with nw.App.crashRenderer() will generate crash dump files in ~/Library/Application Support/<app-name>/Crashpad/completed/. Then decode the crash dump with minidump_stackwalk without symbol files to get the missing modules with hashes.

For 0.13.0-beta6, the expected hashes of crash dump reported by minidump_stackwalk are:

  • nwjs Helper: 6DF796881593398486DD1562F11FB80B0
  • nwjs Framework: 2076ED1863F130249C6F7AFECAC59FD70
  • libnode.dylib: F19C267F429F37E0AA0721C5FE2719290

However the downloaded symbol files have different hashes:

  • nwjs Helper: 6C36191D656F3A938B5EEF1548F0919E0
  • nwjs Framework: 568D8E03EC8034A5B4EE86434B98E1820
  • libnode.dylib: 38356D52AC5A304AA114817D1E51BFAD0

Also the symbol files contain almost meaningless names like:

MODULE mac x86_64 38356D52AC5A304AA114817D1E51BFAD0 libnode.dylib
FUNC bc0 90 0 __ZN4node8debugger5AgentC1EPNS_11EnvironmentE
FUNC c50 100 0 __ZN4node8debugger5AgentD2Ev
FUNC d50 f0 0 __ZN4node8debugger5Agent4StopEv
FUNC e40 c0 0 __ZN4node8debugger5Agent5StartEib
FUNC f00 1c0 0 __ZN4node8debugger5Agent13ChildSignalCbEP10uv_async_s
FUNC 10c0 10 0 __ZN4node8debugger5Agent8ThreadCbEPS1_
FUNC 10d0 40 0 __ZN4node8debugger5Agent6EnableEv
FUNC 1110 130 0 __ZN4node8debugger5Agent14MessageHandlerERKN2v85Debug7MessageE
@rogerwang rogerwang added the nw13 label Mar 10, 2016
@rogerwang rogerwang added this to the 0.13.0 milestone Mar 10, 2016
ghostoy pushed a commit to ghostoy/chromium.src that referenced this issue Mar 15, 2016
By default, Chrome will generate a fake .dSYM file which doesn't
contain well-formed debugging info.

Fixed nwjs/nw.js#4450
jtg-gg pushed a commit to jtg-gg/node-webkit that referenced this issue Mar 31, 2016
@jtg-gg
Copy link
Member

jtg-gg commented Mar 31, 2016

@rogerwang / @ghostoy now I have problem in nwjs packaging in osx, it says it can't find 'nwjs.breakpad.tar' which was created by dec84d6

so which script should create the nwjs.breakpad.tar now?
and... for OSX debugging do we still use breakpad ? or we tar the .dsym files ?

@jtg-gg jtg-gg reopened this Mar 31, 2016
jtg-gg pushed a commit to jtg-gg/node-webkit that referenced this issue Mar 31, 2016
@rogerwang
Copy link
Member

I think you didn't set mac_breakpad=1. Please refer to the official buildbot for build steps and configurations: http://buildbot-master.node-webkit.org:8010/builders/nw13_sdk_mac64/builds/272

@jtg-gg
Copy link
Member

jtg-gg commented Mar 31, 2016

@rogerwang I've just added mac_breakpad=1, my build still fail on packaging due to missing 'nwjs.breakpad.tar'. it only happens if you start clean / empty because 'nwjs.breakpad.tar' never created if you start clean

@rogerwang
Copy link
Member

It's now done here:
https://github.com/nwjs/chromium.src/blob/nw13/chrome/chrome_exe.gypi#L248

On Thu, Mar 31, 2016 at 1:55 PM jtg-gg [email protected] wrote:

@rogerwang https://github.com/rogerwang I've just added mac_breakpad=1,
my build still fail on packaging due to missing 'nwjs.breakpad.tar'. it
only happens if you start clean / empty because 'nwjs.breakpad.tar' never
created if you start clean


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#4450 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants