Comments (1)
Hiya, I don't have a specific list at the moment, but I can think of a number of 'nice to haves'. I will edit this list as 'reply 1' as others add material so, at least in the short term, it's a useful list. These are in no specific order;
-
Extend the CI testing to perform regression tests: When something gets changed there is always the possibility that we break something that was previously working. It would therefore be useful if we could have some basic tests that we run during the CI to ensure that at least the gross functionality is still operational. I would expect this would be done by 'replaying' captured files into the utilities (via the
orbuculum -f xxx
mechanism or direct file feeding into each utility) and then doing a diff on the resulting output. -
Better project-wide configuration mechanisms. When the tooling is being used on a project then it's configuration doesn't really change, so it would be nice if all of the tools had the option to take configuration from a .orb file or similar in the root directory of the project. Current thinking is that this should be TOML based.
-
Multi-channel orbcat. It would be nice to be able to switch orbcat channels on and off in combination. The idea would be that when a capture has been performed then individual channels in the orbcat can be switched in or out of the flow to bring more or less information into view.
-
Graphics! All the utilities are currently text based. Some people like graphics. It would be nice to be able to offer graphical front ends for the utilities. I would expect they would still run in the same way, but be presented via the nicer UI if folks want that. Some utilities already have some limited capability for this (e.g. the JSON output options on orbtop).
-
Richer orbtop. Integrating orbtop and ncurses would allow users to be able to 'move around' in the loading views to see dynamically where the time is being spent; By file, by function, by line or by assembly instruction. This isn't as painful as it sounds...it's mostly applying the sio.c principles that are used in orbmortem to orbtop.
-
Execution markup from source or PAC file. There is information in the elf and in PAC files that we can use to decorate the execution records to make it more informative. The obvious low hanging fruit here is the interrupt vectors in orbtop, but I think there are plenty more. If we can extract that information we can give a richer record of what the target was doing.
I think that's a reasonable starting list, but I'd love people to make addition suggestions either in reply or via the Discord so we can extend this.
from orbuculum.
Related Issues (20)
- Install more files on Linux HOT 1
- Extraneous arguments in meson.build file HOT 3
- Inconsistent results from orbfifo when reading from file and writing to permanent file HOT 3
- Arch linux builds need a meson prefix HOT 3
- Cannot set server and port in orbfifo HOT 2
- Do not require trailing slash in orbfifo basedir HOT 2
- Cannot abort orbfifo with Ctrl + C when not yet connected HOT 6
- gdbtrace.init does not seem to work with newer version of arm-none-eabi-gdb HOT 7
- Windows CLI output has corrupted characters HOT 2
- orbtop CPU usage increases over time
- Orbmortem save to file not working HOT 2
- 'ARM_INS_ERET' not in /usr/include/capstone/arm.h HOT 2
- orbtop should provide immediate error about missing objdump HOT 2
- orbtop: Exception number format, 0..N vs -16..N HOT 5
- orbtop exception tick count wrong for nested instructions HOT 1
- Weird help message for the orbtrace -T option HOT 1
- Loosely formatted orbcat output specification doesn't result in output HOT 1
- Package binaries along with releases HOT 1
- Orbuculum fails to connect to J-LINK GDB Server on Windows. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from orbuculum.