|
| Re: Eclipse Debugger Usage with gcc on WIndows [message #1864950 is a reply to message #1863768] |
Sun, 21 April 2024 17:31  |
 Ralph Felts
Messages: 1
Registered: April 2024 |
Junior Member |
|
|
Hello,
1. Invoking the Eclipse debugger programmatically can be achieved using the DebugBreak() function. However, DebugBreak() is a Windows-specific function and may not work with the Eclipse debugger. Instead, you can use the raise(SIGINT) function to generate a SIGINT signal, which can be caught by the debugger. Here's an example of how you can use it: geometry dash scratch
c
#include <signal.h>
int main() {
// Your program code here
raise(SIGINT); // Send SIGINT signal to invoke debugger
// Rest of your program code
return 0;
}
When you run your program and it reaches the raise(SIGINT) line, the debugger should be invoked and pause execution at that point.
2. I think the issue with breakpoints in linked source files might be related to the build configuration or the way the files are included in your project. I think you should make sure the linked source files are part of the build configuration. Go to your project properties, navigate to "C/C++ Build" -> "Settings" -> "Build Steps" -> "Build Artifact(s)", and ensure that the linked source files are included.
[Updated on: Wed, 24 April 2024 16:49] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02045 seconds
] 
Search
Help
Register
Login
Home
