Some operating systems have core dumping disabled by default, or they minimize the core dumps to a mini dump, which may help with debugging the application, but will likely be much more limited then a full core dump. This may help to define the bug better and may help to narrow down a test case. In such cases, the engineer will likely want to debug the crash seen, especially if they are a test engineer, to for example get a backtrace (an overview) of what functions were running at the time of the crash etc. The second scenario is a professional (for example an IT consultant or test engineer) running into a crash with an application they also support or maintain. Knowing GDB helps tremendously with this task. This is a common situation, and most advanced users at one point or another will find themselves debugging an application crash. Firstly, there can be an end user running into an application crash who would like to learn a little more about what happened, and figure out if the bug is already known by the community, etc. If you into Windows, then you may like to read Windows Memory Dumps: What Exactly Are They For? instead!įor Linux users, it is important to understand where GDB fits into the process flow when considering computer bugs and errors. It is completely free and can be installed easily on all major Linux distributions. Development on GDB started somewhere in 1986-1988, and in 1988 the tool became part of the Free Software Foundation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |