User forums > Embedded development
Remote debugging issue in 13.12?
oBFusCATed:
Sorry for the late reply.
Can you try to reproduce this problem when running remote debugging with native targets?
I have no hardware that can be used to reproduce the problem, so there is no way I can try to fix it.
But if you can reproduce it with native targets then I can probably reproduce it, too.
DejaVu:
I can confirm this bug (and many more). Whole debugging at Code::Blocks 13.xx suck hard. Issues:
1) IDE adds several times the same breakpoint (it's not checking if breakpoint already exists)
2) Removing double breakpoint removes only one instance. There's no information in IDE that breakpoint is set and IDE still breaks at invisisible breakpoint.
3) Quite often debugging feature hangs when I want to press "continue debugging". It just doesn't respond.
4) The same issue occurs when I would like to stop debugging. I can click button 1k times and still it doesn't respond to any action.
Remote debugging works fine at GDB, so issue is strictly related with Code::Blocks. I didn't have these issues at Code::Blocks 10.xx. Currently I'm searching other IDE for linux, because it seems that Code::Blocks quality lower than I expected. Debugging for IDE is primary feature. If it's not working then IDE doesn't exists. Secondary feature is Intellisense, but Code::Blocks can't deal with loading all symbols for chromium engine (it just closes while loading all files into project). Chromium engine with third party have ~1GB of source files. Third feature is File Searching. It's slow as hell and it's much better to use grep instead fighting with Code::Blocks slow search. Grep is searching phrases 1000x times faster than Code::Blocks.
PS. If you see any reason to split mentioned issues into several bugs/topics please do it. I have just created an account to confirm issues with remote debugging. If I won't find alternative then maybe I will spend few days to fix remote debugging at Code::Blocks, but currently amount of other issues suggests that other IDE should be picked even if license won't be for free.
I must add that few years ago I was thinking that Code::Blocks will catch up Visual Studio but it seems that performance of each tool in C::B is horrible and software stability is quite low (unacceptable IDE for professional development).
"Can anyone help us solve this problem in 13.12?":
1. make code review of whole remote debugging
2. make diff what has changed with debugging between 10.xx and 13.xx
/edit: 3. blame files related with remote debugging and check what was changed and analyze if changes have sense.
ca. 2 months have passed already since this topic was created and IDE still is unstable.
oBFusCATed:
--- Quote from: DejaVu on March 05, 2015, 12:46:08 am ---ca. 2 months have passed already since this topic was created and IDE still is unstable.
--- End quote ---
2 months have passed and no one (including you) has posted the exact steps needed to reproduce the problem.
I don't do remote debugging at all (and I have no embedded devices I can test with) so I don't test this feature of Code::Blocks.
Post the steps and I'll try to fix it. If I can't reproduce it I can't do much about it. Sorry.
Same for the other 4 points related to debugging - post exact steps and sample projects and I'll try to do something about it.
p.s. debugging with 10.xx was a disaster and I don't understand why people continue to think it was any good!
p.p.s. cb won't be able to be as good as vstudio, for the simple reason that no one is working on it as a full time job. vstudio team is comprised of tens or even hundreds of people.
MortenMacFly:
I think it should be possible to try remote debugging with a local loopback adapter. This means, start gdb server and connect to it using 127.0.0.1. This should use the same code portions as if you would connect to a remote device.
oBFusCATed:
Morten: I know, this is the reason why I asked if the problem can be reproduced with a native target.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version