Re: [Anjuta-list] Cross debugging?



Biswapesh:


I'm looking at using Anjuta for some cross development (arm-elf).  I
quickly figured out how to tell Anjuta to invoke something other than
the default compiler, how do I do that for the cross debugger?

If you're using the latest stable version (i.e. 1.0.2), then the option
should be in Settings->Preferences->Build. I guess it's a bit hard to
find - maybe we need a seperate debugger tab ?


Ok, got that now. I start the debugger, then use Debug|Custom command to source a script that establishes a connection with my debugging target (remote, over a serial connection). So far, so good.

But Anjuta won't step. I press F5, and it stays "stuck" at the first source line in the application. F8 works, but F6 and F7 are grayed out. Each time I press F5 or F8, I get a terminal window that goes away in a second or so later...


Ideas?


I think that if Anjuta for crossdevelopment takes off (I hope it does, you're much closer than KDevelop), you'll want a separate debugger tab to help set up things that my script is doing--- establishing the remote connection at a specified bit rate or IP address/port, loading the application, setting a temporary breakpoint at main and continuing to that breakpoint (optional, not all users will want this).

Take a look at Insight's configuration settings for what I'm thinking of.



b.g.


Thanks!


b.g.
--
Bill Gatliff
Embedded Linux development and training services.
http://billgatliff.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Anjuta-list mailing list
Anjuta-list lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/anjuta-list


--
Bill Gatliff
In the dark on embedded Linux?	Step into the light.
http://billgatliff.com






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]