-
Notifications
You must be signed in to change notification settings - Fork 100
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
Document User Journey #401
Comments
I'll pick that one ^^ 👋 |
Update: I didn't start it at the moment. I'm trying to finish and release this one: nodejs/diagnostics#572 Then I'll jump on it ^^ |
No worries - I forgot to mention these videos of @watson and @joyeecheung may bring some inspiration too Joyee/Thomas Brought you into the thread incase you had some tips/pointers/collateral for this documentation. |
For inspiration too: https://blog.cjihrig.com/postmortem_debugging (cc @cjihrig) |
Hi there 👋 For the delivery of this task, I propose:
WDYT? |
Hey people 👋 Sorry for the wait. We finished the structure of the post, now I'm trying to play with I'll keep you informed, but the delivery will take longer than I expected. |
Update: I tried on an Intel machine, and it seems to work pretty fine 🎉 I'll continue my experiment with my wife's laptop 😅 (and will probably raise an issue on apple's side). |
@No9 on my wife's laptop xcode was installed (then with lldb within). I install I'll be able to continue my exploring phase :) (and will raise an issue to Apple for M1 issue) |
Hey team! For various reasons, it took me more time than expected to finish that documentation. I often approach this kind of exercise by practicing with the tool, but in my case, it's difficult: I have to borrow a machine, and sometimes I face difficulties with the tool itself (#422), making progress difficult (regarding the time I have) If someone wants to jump on it, please do it. I also consider just reshaping past articles from IBM and Colin, but I already observe that Any thoughts? concerns? |
No problem at all, @tony-go. Leave it open and if someone is interested in helping you. They will contact you. |
As per the general drive to document user journeys in node tooling this issue is to track the creation of an llnode tutorial as part of
nodejs/diagnostics#502
The next step would be to review content that is already available and map out a tutorial structure
This post may be a reasonable starting point.
https://developer.ibm.com/articles/explore-nodejs-core-dumps-using-the-llnode-plugin-for-lldb/
The text was updated successfully, but these errors were encountered: