I want to share some knowledge about constructing an external loader for an ST project. After long days, undergoing mysterious errors and bad documentation, I finally built a functional loader. I will not teach how to do it but simply explain how it works and point some issues that I came across (my experience =)).
This year has been an awkward one. All COVID-19 situation has been changing a lot the way we work. Suddenly everyone needs to start to work remotely and learn new tools to do so. I had been learning a lot of terminal tools and using a minimal graphical interface as much as possible in my daily activities, just for fun. So this transition to remote work was, basically, in my environment, with an ssh connection in the middle. One of the tools that I’ve started to use more often was gdbserver.
In this guide, I am going to give you a quite basic tutorial on how to use gdbserver to debug your Linux application.
Some time ago a friend told me that writing my posts in English would be a good idea to reach more interested people and to improve my English skills. So it is time to start writing in English.
Core Dumped. Have you ever seen this message after your application crashes? Do you know that it is possible to get the inner state of your application after it crashed and debug it? Yes, it is possible with the core dump feature.
Como comentei em outro post, tenho usado muito o terminal ultimamente em meus trabalhos. E além do fish e o vim, um outra ferramenta que tem me proporcionado um bom desempenho é o tmux.
Tenho usado muito o editor de textos do terminal Vim esses últimos dias. Uso tanto em casa, como no trabalho, seja no desenvolvimento das minhas aplicações, quanto para escrever esse post. Chegou a um ponto que senti a necessidade criar uma configuração para me deixar mais à vontade, pois me vi replicando as mesmas configurações uma a uma, entre os computadores. Então, partiu dar uma estudada em como realizar essa tarefa e criar um arquivo de configuração do Vim, o vimrc.
