-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
TriCore support #1144
Comments
Hi, thanks for the suggestion. Unfortunately, this arch seems to be very niche and unless any of the devs gets a reason too, it's unlikely we're going to implement this support. If you feel like trying to integrate, PRs would be welcome but considering it's non standard (and even requires a specific GDB version) it would be to be added in gef-extras, not gef itself. Cheers |
Understandable. Unfortunately I probably won't have the time to do it myself anytime soon so we can close this request I think. For now I've managed to get Thanks for the quick reply! |
Glad you found a good fix then! 👍 I'll be closing it, if you ever get a chance to work a PR for GEF you can always link this issue. |
Type of feature request
New architecture support/Existing architecture improvement
Misc
No response
Summary Description
I'd like to request support for the TriCore intruction set.
I'm currently using the https://github.com/volumit/gdb-tricore fork of gdb that supports debugging TriCore but gef currently doesn't seem to handle the architecture well. The colors are there but displaying code, registers, stack seems to be broken.
For context, I am using QEMU to actually run the TriCore binaries (in system mode) and attaching to them using
gef-remote
.Implementation idea/suggestion
Get the nice default view of gef (where it displays the registers, code, stack, etc) working with QEMU emulated TriCore binaries.
Existing alternatives?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: