|
|
Re: New Breakpoint causes SIGINT to process under debug [message #1848368 is a reply to message #1848350] |
Tue, 30 November 2021 00:09 |
Gianluca Sorrentino Messages: 5 Registered: November 2021 |
Junior Member |
|
|
You are right about GDB sending SIGINT to the process (i'd say kind of obvious) but Eclipse controls GDB and this behavior does not occur with netbeans (for example).
Adding a new breakpoint (i'm guessing here, but with some confidence) is done by Eclipse passing the request to GDB, and here i think is where the problem comes from.
GDB is perfectly capable of not having to terminate the process to add a breakpoint live, as proven by other IDE... i have 0 knowledge about GDB and its interface but out of experience i can't help to blame Eclipse for this behavior of GDB (happy to be proven wrong if i am, there is always to learn).
It might just be that Netbeans and others use some sort of workaround when they detect issues with breakpoints, i simply don't know how they manage the case, but for sure they can navigate the issue.
Best Regards
[Updated on: Tue, 30 November 2021 00:12] Report message to a moderator
|
|
|
|
|
Re: New Breakpoint causes SIGINT to process under debug [message #1848440 is a reply to message #1848378] |
Thu, 02 December 2021 08:07 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
You do realize that CDT is a plugin to Eclipse, yes? It uses the
editor framework but I don't see how the Java plugin affects
it.
GDB was likely chosen because of it's popularity, particularly
in the Linux world, is multiplatform and open source. The
debug interface in CDT is built around GDB. Using something
else probably would require a lot of effort.
You could of course volunteer if you think another debugger is
better and worth the time or maybe you can ask for your money
back.
[Updated on: Thu, 02 December 2021 08:15] Report message to a moderator
|
|
|
Re: New Breakpoint causes SIGINT to process under debug [message #1848462 is a reply to message #1848440] |
Fri, 03 December 2021 02:35 |
Gianluca Sorrentino Messages: 5 Registered: November 2021 |
Junior Member |
|
|
Just for clarity i wish to say that nothing i wrote was a complaint but merely a list of observations which i think you read from the wrong angle.
* I understands CDT is a plugin of Eclipse and I never implied that such aspect has anything to do with technological limitations of Java or whatever you think i said... my point was simply that it is possible that JAVA is easier to deal with when piloting the debugging process from the GUI/Editor (due to indirect code execution offered by the JVM) and that might have had an impact (initial lack of knowledge / architectural limitations / etc) when Eclipse has been extended (with a plugin) to C/C++.
* I never suggested GDB was not the right choice. My remark about its stability was just to make clear that i might expect to blame GDB sometimes and not necessarily the editor (misusing it): though i don't believe this is the case, so i posted this report.
* I don't think i was offending or demanding anything by reporting a problem with the software, normally developers are happy (at least i am) when they get a bug feedback because they can improve their creation ;)
[Updated on: Fri, 03 December 2021 02:36] Report message to a moderator
|
|
|
Re: New Breakpoint causes SIGINT to process under debug [message #1848463 is a reply to message #1848462] |
Fri, 03 December 2021 05:33 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
Quote:don't think i was offending or demanding anything by reporting a problem with the software
No offense taken but, as stated, the issue is inherent in the way GDB operates with
nothing to do with CDT thus generally out of the hands of CDT developers. You
did, though, seem to be suggesting that someone (else) volunteer their free time
and effort into using another debugger and perhaps didn't realize it.
The best way to handle such change is to submit an enhancement request
through bugzilla where it might spark someone's interest -- particularly if it would
amount to a minimal change -- then willing to devote time into continued
maintenance. Chances are that might only be you and perhaps a few others.
Or, better yet, develop a CDT plugin to use another debugger and offer it to the
public and see how much interest it garners. This has been done with other
plugins (R from StatET for instance)
[Updated on: Fri, 03 December 2021 05:53] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03890 seconds