MagicBane
/
Server
92
0
Fork 2
Code Issues 7 Pull Requests Projects Releases Wiki Activity

Update 'Debugging with MagicBox'

master
MagicBot 3 years ago
parent
9ee37ff072
commit
fbd8a39b0a
1 changed files with 13 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 14
      Debugging-with-MagicBox.md

14
Debugging-with-MagicBox.md
Unescape

@ -42,4 +42,16 @@ Use this new configuration to connect your IDE to MagicBox. The game will begin @@ -42,4 +42,16 @@ Use this new configuration to connect your IDE to MagicBox. The game will begin
Breakpoint was hit!
![breakpoint](https://cdn.discordapp.com/attachments/534260038039109632/970665403376357416/unknown.png)
![breakpoint](https://cdn.discordapp.com/attachments/534260038039109632/970665403376357416/unknown.png)
### Profiling your code
Another important aspect of development is to profile your code. Not just to see how slow your new routine runs; the profiler will catch every error masked due to empty try-catch blocks. It will tell you when you are generating 2000 objects a second. Your new branch might appear to be running fine but have *hidden issues*.
![profiler](https://media.discordapp.net/attachments/398576832485654529/513765550506377257/unknown.png?width=877&height=335)
There are many choices available free and otherwise for Java profilers. We have tried most. The Profiler of choice for the Magicbane team is [YourKit](https://www.yourkit.com/). The game has built-in support for profiling as it does debugging.
`./mbstart.sh -profile`
The YourKit agent is not being shipped with the image. Choice of profiler is the perrogative of your team.

Write Preview
Loading…
Cancel
Save