Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-debug-dev] Crashes with large makefile imported

[Trying again to mailing list this time]

I apologize if there's a duplicate in this list somewhere, I looked through
the forum, but I didn't see anything quite like this.

I have been using Eclipse and CDT on my own for home grown projects for
about a year now.  I've honestly enjoyed it and it's made my development in
Linux so much more enjoyable.  In fact, I liked it so much, I was able to
convince several people at work to start trying to use it for a development
environment for our work projects in Linux.  Unfortunately, our makefiles
are so complex and our projects so large, it's crashing Eclipse all over the
place.  

What I've noticed is that when I first pull in my C++ make project, it
starts to import everything just fine.  However, right at the end of
importing the file, it usually crashes Eclipse out.  Then when I re-entered
Eclipse (sometimes I would have to restart X windows), I could start the
build, but it would crash right away.  One thing I found out is we had alot
of warnings (over 500) on one of our files, so I hacked the file so it
wouldn't dump out so many warnings.  This allowed CDT to proceed further. 
[So #1 CDT doesn't appear to handle a fast dump from the command-line of
large amounts of warnings'.

Next it started crashing after about every 4 minutes in the build.  What I
figured out is the command-line for the console output was 500 lines.  I
bumped this up to about 8000 lines, and it built for much longer.  But
again, after a certain amount of time (usually towards the end of the build)
it would still crash eclipse.  Again, just as above, I think it might be
related to the number of lines or something.  But I was afraid of bumping of
the line limit too much for fear of killing the memory footprint.

Now, it crashes on me even going into Eclipse (it has my CDT project as the
default starting enviorment).

What really annoys me, is everytime it crashes, the error log has some
generic message about something bad happened so Eclipse died.  Here's one of
the log files.   http://www.nabble.com/user-files/235870/hs_err_pid9751.log
hs_err_pid9751.log .

I'd really like to get this working since it would make our development and
debugging lives in Linux alot happier.

So I'm willing to try some things out.  Also, is it possible to get CDT to
output more information?  Perhaps even during the import?  

I tried building a debug version of Eclipse, but the build failed on my
system.  So I'm just having to live with the release build for now.

Thnx,
OpenGL Programmer
-- 
View this message in context: http://www.nabble.com/Crashes-with-large-makefile-imported-tf2221208.html#a6153450
Sent from the Eclipse CDT - debug forum at Nabble.com.



Back to the top