-
-
Notifications
You must be signed in to change notification settings - Fork 345
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
Fix/gdbstub continuation crash #1671
Merged
slaff
merged 14 commits into
SmingHub:develop
from
mikee47:fix/gdbstub_continuation_crash
Apr 14, 2019
Merged
Changes from 11 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
0e294b1
Fix warnings in STRICT mode
mikee47 8eebece
Simplify code now that `m_printf` supports flash strings directly
mikee47 5d0a992
Add missing `return` statements in LiveDebug sample
mikee47 854d393
Improve gdbstub debugging
mikee47 244123f
Define `SimpleTimerCallback`
mikee47 7c1bc29
Fix issue with debugger break during syscall
mikee47 12cf0b9
Add `queueBreak` command to check problem with stepping
mikee47 f5da3f9
Fix single-stepping issue by raising interrupt level in `gdbstub_icou…
mikee47 54bb3c4
Updates to gdbstub code following review
mikee47 6f4fd5b
LiveDebug sample updates
mikee47 5a70f09
Remove `GDBSTUB_PAUSE_HARDWARE_TIMER` option and related code - it do…
mikee47 0860d42
Copy symbol files only when ENABLE_GDB=1
mikee47 a800a42
Check build in STRICT mode
mikee47 e422d03
Redefine `gdb_do_break()` as macro
mikee47 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, make
GDBSTUB_ENABLE_SYSCALL
to be0
by default. This will help visual debuggers behave as expected. Allow also that setting to be changed during compilation so that adventurous developers can try it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To keep the instructions simpler, how about we do this?
To build for normal (command-line GDB) use:
make flash
To build for eclipse:
make flash ENABLE_CONSOLE=0
The problem is specific to the
LiveDebug
sample.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use
ENABLE_SYS_CONSOLE
instead ofENABLE_CONSOLE
. In addition I would prefer the syscall stuff to be disabled by default. For the LiveSample we can enable it by default by writing in the Makefile-user.mk.When
ENABLE_SYS_CONSOLE
is enabled a warning message should be shown to inform the developers that this might interfere with visual debuggers, like Eclipse. And that it can be disabled usingmake ENABLE_SYS_CONSOLE=0
.What do you say?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or even better
ENABLE_GDB_CONSOLE
instead ofENABLE_CONSOLE
. The name prompts that this is related to the special GDB console.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The simplest way is to just edit the
gdbstub-cfg.h
file directly to make changes as required (same goes forgdbcmds
). I also have a note in thereadme.md
about usingUSER_CFLAGS
to set these values for a particular project - I've done this for theLiveDebug
sample as per your suggestions.Are you propsing we add the abillty to change these directly from the
make
command line?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I see. Then can you do the the following?