Closed Bug 1596695 Opened 5 years ago Closed 5 years ago

ask for permission to upload symbols for yhuang@mozilla.com

Categories

(Socorro :: Symbols, task)

Product:
Socorro
Component:
Symbols
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: allstars.chh, Assigned: willkg)

Details

signed in my LDAP in https://symbols.mozilla.org/ but it says I don't have permission to upload symbols, file this bug to request it.

Generally, we don't hand out symbols uploading permissions. Can you tell me more about what you're trying to do? What kinds of symbols are you planning to upload?

In my own build of m-c, I met some crash, and I'd like to submit my crash-report, (or let other engineers to look at the crash report).
And when I got the crash and saw the crash report, I found out the function signatures are all hex numbers, I realized then that's because the Socorro doesn't have my debug symbols, so I'd like to upload one.

You can look at the crash - and generate a stack trace - locally. It's much simpler and much faster than uploading everything for processing. Send me an e-mail and I'll send some instructions your way later tonight.

Given that, I'm going to mark this as WONTFIX.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

Then I don't understand why you put
"You have the following permissions:
None! File a bug to ask for permissions.
Don't forget to mention the email you used to sign in."
on symbols.mozilla.org, I saw the message I think it's O(1) thing, just request for permission and it's done.
if a developer cannot unload symbols, just don't put that sentence, It's wasting everyone's time to spending time to discuss this, and then, bang, we don't do this normally, "CLOSE this as WONTFIX".

Generating a stack trace is easy, but the problem is I have to reproduce it, record it, and post it somewhere.
then I posted the data on bugzilla, then the dev said, oh, we need more information on another thread,
then this goes again, I generate the stack trace, then he/she asks can I also attach more system information?
I have to go back and forth 3~4 times to the let dev have enough information, but isn't this crash report all about?

I have run into this many times, I try to fix my bug, and I met some crash unrelated to my bug,
I filed this on bugzilla, then I was asked to provide more information than just the stack trace, and this goes a few times.
The time I spent on an unrelated bug is more than what I was spending on my bug.

It would be really great that I could just submit the crash report in my local dev build with symbols.

I'm really sorry that you're frustrated and I completely understand what you're going through.

The symbols server is not intended for personal builds. It's intended for official builds and try builds generated by taskcluster. Generally, people aren't trying to upload symbols, however, it's not uncommon for maintainers of Linux packages to want to upload symbols for their builds of Firefox or system symbols or other related things. It's pretty unusual for a Firefox engineer to end up on that page looking for solutions to the problems you're having. That's been our experience and why the page is designed as it is.

Gabriele offered to walk you through what you need to do. I think that should help. If it doesn't, we hang out on #breakpad on Slack--hop on and someone can help you there.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Gabriele just pinged me on Slack and walked me through what you're trying to do and the bits I didn't understand. I've granted you symbols upload access.

You're going to need to create an API token to upload symbols with. When you create that key, please create it with Upload Try Symbols Files. That way your personal build symbols don't get mixed up with official/release build symbols which creates problems that are hard to figure out.

Let me know when you've got things working.

Sorry for the frustration! If you have problems. we hang out on #breakpad on Slack.

Assignee: nobody → willkg
Status: REOPENED → ASSIGNED

Cheng-Hao Huang: Is this working for you?

Flags: needinfo?(allstars.chh)

Sorry, I happen to be sick these few days.
The symbol uploading works for me, thanks. (the symbols are from the try)
One question is, now in my crash-report, how do I get the crash-report to have my uploaded symbols?
Because my crash report (from my local build) still cannot resolve the symbol.

Thanks

Flags: needinfo?(allstars.chh)

(In reply to Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh] from comment #9)

Sorry, I happen to be sick these few days.
The symbol uploading works for me, thanks. (the symbols are from the try)
One question is, now in my crash-report, how do I get the crash-report to have my uploaded symbols?
Because my crash report (from my local build) still cannot resolve the symbol.

If you sent the crash report before uploading the symbols then it needs to be reprocessed; all crash reports sent after you've uploaded the symbols should have the symbols set correctly.

My symbol from try : https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/KBmjctXmT9e6GZwM8-6kfQ/runs/1/artifacts/public/build/target.crashreporter-symbols-full.zip

and after I uploaded my symbol, I tried to reproduce to crash
run with ./mach run --enable-crash-reporter (my mozconfig also has ac_add_options --enable-crashreporter)
(the commit is the same commit pushed to try to have the symbols)

Then I reproduced the crash
checking about:crashes, then submit the crash report
it still has no symbol
https://crash-stats.mozilla.org/report/index/9fd88c2c-e9b0-4925-a09a-a4bcc0191122

Any step I am missing?

When you're running your local build with ./mach run --enable-crash-reporter did you use the artifacts from the try build? Or is libxul.so the one you compiled yourself? I can see in the crash report the debug ID for libxul.so is BF9A7C96C64B84B5B7AC4CD40CDFAE4A0 while the symbol archive contains two different debug IDs for libxul.so: 59E38270CC268B9C29794982D3EFA1580 and D3A61DBB9D8EDB7566F28BF3EF293AE40. If they don't match then the crash won't be symbolicated.

You can do two things to make sure they match: either you cause the crash with the executable and libraries from the try build or you build symbols locally (./mach buildsymbols) and upload them manually. The latter option is quite cumbersome (and slow unless you have a very, very fast internet connection) so I suggest using the try build if possible.

I see three upload records:

https://symbols.mozilla.org/uploads/upload/105655

That says that all the files were skipped because it already had them all. The libxul in that upload round had this debug id: 59E38270CC268B9C29794982D3EFA1580

https://symbols.mozilla.org/uploads/upload/105368

Half the files were skipped because they were already there. The libxul in this upload round was uploaded and has this debug id:

59E38270CC268B9C29794982D3EFA1580

https://symbols.mozilla.org/uploads/upload/104420

All of the files were accepted. The libxul in this upload round was uploaded and has this debug id:

54739FFD19122E292DF07B141AFDF9000

The one in the stack in the crash report has this debug id:

BF9A7C96C64B84B5B7AC4CD40CDFAE4A0

Are you sure those are the symbols that match the build you're crashing from? I'm not sure how to verify that, but it seems like that's the problem you're hitting.

Now I use the symbols with ./mach buildsymbols, now the crash-report will have the function signatures.
This is super awesome.
Thanks

Glad to hear you got it working! Sorry it was such a hassle!

Status: ASSIGNED → RESOLVED
Closed: 5 years ago → 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.