Update tizen_gdbserver_run script for tizen 10#72364
Update tizen_gdbserver_run script for tizen 10#72364antonijakubiak-samsung wants to merge 5 commits into
Conversation
There was a problem hiding this comment.
Code Review
This pull request refactors the Tizen gdbserver runner script to launch applications in native suspension debug mode and manually attach gdbserver to the process PID. Feedback highlights two main improvements: replacing the non-portable grep -oP with a more portable sed command to extract the PID on macOS hosts, and conditionally appending $APP_ARGS to avoid trailing double-dashes when no arguments are provided.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
PR #72364: Size comparison from f1767a8 to a139307 Full report (35 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #72364 +/- ##
==========================================
+ Coverage 55.55% 55.61% +0.05%
==========================================
Files 1630 1630
Lines 111147 111146 -1
Branches 13410 13397 -13
==========================================
+ Hits 61752 61812 +60
+ Misses 49395 49334 -61 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Fix Tizen remote debugging helper script (
tizen_gdbserver_run.sh)__DLP_DEBUG_ARG__and__AUL_SDK__) with the officialapp_launcher --debug --startAPI to ensure compatibility with Tizen 10.0 images.gdbserverto the suspended process.Testing
Run application in debug mode:
Run debugger:
Setup debugger:
Trigger breakpoint:
Results in GDB:
Readability checklist
The checklist below will help the reviewer finish PR review in time and keep the
code readable:
descriptive
“When in Rome…”
rule (coding style)
See:
Pull Request Guidelines