Moderators: simonsunnyboy, Mug UK, Zorro 2, Moderator Team
JustinPayne wrote:For those writing ST/TT/Falcon apps using GCC or G++, how are you performing your debugging? When I say, "How", I mean, in detail, what tools are you using, what environment are you doing this in, how would I set myself up to do it the same way, etc?
JustinPayne wrote:For those writing ST/TT/Falcon apps using GCC or G++, how are you performing your debugging? When I say, "How", I mean, in detail, what tools are you using, what environment are you doing this in, how would I set myself up to do it the same way, etc?
wongck wrote:For my current project (I hope to release soon for 2014), I used only the printf statements.
Sure it is a hassle to type a complete printf statement to see the data but it works.
jfl wrote:Doesn't your editor handle macros? That's what I do with QED. I have a printf() statement binded to a function key. A form_alert() string to another key, etc. Makes life much easier. You just need to type the value you want to print.
JustinPayne wrote:As far as debugging, printf() would probably work but I use Eclipse a lot for Java and stepping code is a common occurence, one that is hard to break. Even when I did Assembly Language back in '92 I used breakpoint to step through the code. Printing debug always reminds me of debugging scripts.![]()
JustinPayne wrote:As far as debugging, printf() would probably work but I use Eclipse a lot for Java and stepping code is a common occurence, one that is hard to break. Even when I did Assembly Language back in '92 I used breakpoint to step through the code. Printing debug always reminds me of debugging scripts
jfl wrote:I use GCC on my FireBee (no cross compiling for me) and did try GDB a while ago but soon found it was more trouble than it's worth. With the maximum set of warnings GCC catches a lot of my mistakes and as for the rest, well, I try not to introduce bugsBut when I do, printf() is still my favourite method. It forces me to understand what I'm actually doing.
I also used Lint for a while, and it did catch some suspicious stuff in my code, but again I found that my time was better spent trying to learn to program properly. I suppose I'm kinda old school...
dml wrote: I suppose if you're using GEM this would not be very practical though.
wongck wrote:LOL... if you have 4 Gigs... that's definately more than enough for Mint.
I have less than that on my Falcon/CT63 system.
You mean 4MB I guess.
Ah yes, Eclipse was one of those IDE that I was going to use for debugging applications on the Falcon.
Just set that up as the gdb client and you should be able to do it.
wongck wrote:Picked up some chatter over the mint list channel. Last year someone talking about possibly new IDE for the Atari. Wonder how's that getting along.
May be JFL or Joska knows more of the on-goings there.
jfl wrote:An IDE has been an on-and-off subject of conversation over the years.
Users browsing this forum: No registered users and 2 guests