Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.
  1. Home
  2. Discussion Forum
  3. AROS FORUMS
  4. Development General
  5. Debugging with gdb

Debugging with gdb

Last updated on 2 days ago
Track threadPrint
A
aros-sgJunior Member
Posted 2 days ago
#1
Replying in other thread is not allowed (?) so here some more tips:

You can break into the debugger by pressing CTRL-Z in the terminal where AROS was started from.
You can tell the debugger to continue AROS execution with "cont". Sometimes needs to be entered twice (or just press RETURN again).

You can load all symbols for all modules with "loadmods".

If you want to find out the exact name of a library function (they annoyingly have the lvo number as part of the name). You can do like this

Code Download source


info functions OpenWindow


Then you can do

Code Download source


b Intuition_101_OpenWindowTagList


To add a breakpoint when window is open. Then you can start your program and it will break into the debugger when your program's window gets opened.

Then you can do

Code Download source


loadbt

b FunctionInMyProgram


to break at some other place in your program. So no need to necessarily always set up breakpoints in the program itself manually.
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.
Moderator: Administrator, Moderators
Users who participated in discussion: aros-sg