From: Ian G. <ilg...@ya...> - 2011-02-04 19:53:43
|
Hello all, I run rosegarden from within KDevelop4 when doing development. I've only ever developed from within IDEs and I'm hopelessly addicted to them. Command line compilation brings me out in a cold sweat. With RG I normally use KDevelop4 for managing the file editing, running the compiler and having that quick link between the compiler errors and the lines of code where the errors are. The only success I've had running RG under the debugger and being able to do stuff like hit breakpoints, step over/into/out of lines of code and inspect variables is when I've compiled it with the -g -O2 flags - i.e. with debug symbols and optimised. If I don't do the -O2 it runs very slowly, but if you do use -O2 the optimiser musses up your ability to step through some bits of code or view the variable values (only some though, by no means all). Having a navigable stack trace in KDevelop4 when the thing crashes I find very useful. I'm going to loose 1 million linux points when I make the following statement - I find the intellisense and code completion of KDevelop4 absolutely invaluable. It even understands doxygen formatting, so sometimes when you hover over a class or variable you get the full documentation exploding up from your mouse. Navigating from function calls to their declarations/definitions at the click of the mouse is very nice. There, I said it. I should be reported to the linux council of elders now and stoned to death or something, or at least be forced to use autoconf and VI until I've learned my lesson. I daresay with a bit of futsing I could get some improvements with the debugger behaviour. I don't know why I need the optimistion to be honest, but I've never bothered bottoming the issue out. For my practical everyday purposes the way I have my system set up suits my needs, but it would be nice to be able to step through the code a bit more reliably without having to turn the optimisation on. It would be easier in KDevelop4 if we had a cmake script for managing the project. It's one of the things I'd like to volunteer for later in the year. I love CMake! I'll give it another test without -O2 later on, see what happens. I get the feeling that GDB isn't the greatest tool for stepping through code though. Quite often GDB just gives up entirely when I'm stepping through. Cheers all, Ian. From: D. Michael McIntyre <mic...@ro...> To: ros...@li... Cc: Sent: Friday, 4 February 2011, 19:19 Subject: Re: [Rosegarden-devel] Trying Rosegarden in Eclipse On Friday, February 04, 2011, Julie S wrote: > jackd watchdog: timeout - killing jackd > > I'm not even running jack. You are, you're just not aware of it. Rosegarden tries to start JACK if it's not running, and that message tells me that Rosegarden got JACK going. Shortly after Rosegarden crashes (or probably when it exits normally too), you can expect one of those messages on the console. Yesterday, in fact, I kept getting confused because my core dumps were coming from jackd instead of Rosegarden. What was happening was Rosegarden was doing a core dump, and then jackd was following up with another core dump, writing over top of the first one. I edited ~/.jackdrc to say something stupid, so JACK would go away temporarily. > I'd like any suggestions on how to get the debugger working better. I've never enjoyed any success in this area, and I'm afraid I have nothing to suggest. -- D. Michael McIntyre ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Rosegarden-devel mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |