Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Frame issue with the debugger plugin
oBFusCATed:
--- Quote from: scarphin on March 31, 2015, 02:11:42 pm ---gdb/mi seems to be more stable than it currently looks and I think gdb/mi is the way to go. I may provide patches for added functionality and bug fixes. I don't have much experience with test cases but you've already provided an almost working plugin and many test cases to follow so I may add functionality first and then add test cases (I know it should be the opposite btw). I'll post my patches to the corresponding thread, it's up to you if you value them or not. ;)
I attached a patch demonstrating the necessary changes, thanks for your help.
--- End quote ---
I don't intend to do any work on the gdb/mi plugin before I can find some time to design a regression test system.
If there is not such system adding new features is extremely hard, because it is pretty easy to break old features.
Then you can fix the old feature, but you then break something else and you're running in circles wasting time.
This is the reason, I've left the plugin in a non-compilable state, so people are not wasting time trying to use it.
I have some more important tasks to finish first and probably then I'll try to continue working on it.
For the current patches, you can put them on github as a pull request, so they are not forgotten, but I don't intend to integrate them because of the aforementioned reasons.
oBFusCATed:
About the gdb/cli patch:
Can you replace the wxstring::format with the usage of operator<< and see if it works correctly?
The reason I'm asking this is that the different format specifiers can have different meanings on different OSes, so I think that operator<< will be safer.
scarphin:
I too didn't like the format specifier defaulting to '%llu' for both 32-bit and 64-bit platforms but it looks like 'wxString' doesn't have an 'operator<<' defined for 'long long' type:
http://docs.wxwidgets.org/trunk/classwx_string.html#concat
What do you suggest?
oBFusCATed:
Use:
1. stringstream, not sure if it really good idea
2. SCNu64 defined in inttypes.h -> str.Format(wxT("frame %" SCNu64), number) I'm not sure how portable is this
3. Use uint32_t for the frame number
If I were you I'd try 2 and 3 and if I couldn't make it will do it with 1.
scarphin:
1- Me neither!
2- Will that be more portable than 'llu'?
3- That doesn't work already.
I think it will be best to stick with 'llu' for now until cb gets upgraded to a higher wxwidgets version in which wxstring has an operator<< for 'long long' type. Or conditional compilation?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version