Home » Language IDEs » C / C++ IDE (CDT) » Debug doesn't start: Errors exist in a required project
| Debug doesn't start: Errors exist in a required project [message #155550] |
Mon, 03 October 2005 12:13  |
Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
Switching from Eclipse 3.0/CDT 2 to Eclipse 3.1/CDT 3.0 I failed to
start debugging - always the message appears "Errors exist in a required
project". Launch not even is continued, when pressing "Yes". There is
only one project, just containing a main.cpp, where debug starts, but it
fails for all my larger projects, so this is no basic problem of my
configuration, like no gdb in path.
Using the former version, I got this message after every clean build,
but I only had to change some sourcecode and debugging starts after
building - but now this doesn't work any more.
Does anyone know, what causes this message and prevents debug from
starting? What kind of error does it mean - there is no error! The
project was successfully built and I can start the projects "exe"-file
out of the debug-directory. It contains debug information - easy to see
because of beeing very large.
I also know how to make a debug configuration and I made several times a
new one - no change. I tried "Build Automatically", cleaned all several
times, checked the FAQ and so on, but nothing shows me a way to start
debug. I tried to search this group, but google doesn't seem to know it.
What's to do now?
|
|
|
| Re: Debug doesn't start: Errors exist in a required project [message #155576 is a reply to message #155550] |
Mon, 03 October 2005 15:26  |
| Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
> Switching from Eclipse 3.0/CDT 2 to Eclipse 3.1/CDT 3.0 I failed to start
> debugging - always the message appears "Errors exist in a required
> project". Launch not even is continued, when pressing "Yes".
This is a bug in the Eclipse platform. Unfortunately, it prevents to start
the debugger if there is bug in your project. It has been fixed for the
Eclipse 3.2, but for some reason didn't make in Eclipse 3.1.1.
So, the only way to get around it is to find out why Eclipse "thinks" that
your project contains errors. This is more a build or workspace question.
"Edzard Egberts" <e.egberts@tantec.de> wrote in message
news:dhr791$9aj$1@news.eclipse.org...
> Switching from Eclipse 3.0/CDT 2 to Eclipse 3.1/CDT 3.0 I failed to start
> debugging - always the message appears "Errors exist in a required
> project". Launch not even is continued, when pressing "Yes". There is only
> one project, just containing a main.cpp, where debug starts, but it fails
> for all my larger projects, so this is no basic problem of my
> configuration, like no gdb in path.
>
> Using the former version, I got this message after every clean build, but
> I only had to change some sourcecode and debugging starts after building -
> but now this doesn't work any more.
> Does anyone know, what causes this message and prevents debug from
> starting? What kind of error does it mean - there is no error! The project
> was successfully built and I can start the projects "exe"-file out of the
> debug-directory. It contains debug information - easy to see because of
> beeing very large.
> I also know how to make a debug configuration and I made several times a
> new one - no change. I tried "Build Automatically", cleaned all several
> times, checked the FAQ and so on, but nothing shows me a way to start
> debug. I tried to search this group, but google doesn't seem to know it.
> What's to do now?
|
|
|
| Re: Debug doesn't start: Errors exist in a required project [message #155614 is a reply to message #155576] |
Mon, 03 October 2005 19:47 |
| Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
> This is a bug in the Eclipse platform. Unfortunately, it prevents to start
> the debugger if there is bug in your project. It has been fixed for the
> Eclipse 3.2, but for some reason didn't make in Eclipse 3.1.1.
Yes, I tried 3.2M2 and it started debugging after showing the message.
That was not quite the thing I anticipated. :o(
> So, the only way to get around it is to find out why Eclipse "thinks" that
> your project contains errors. This is more a build or workspace question.
There are 18 projects (and 4 librarie projects) and every single one
seems to contain the error. I have not the faintest idea, for which kind
of error I should look. It's an error Eclipse 3.0 only shows after a
clean build - so that doesn't seem to be a constant error in my
projects, because it changed depending to sequence of starting debug.
For one project I just made a new workspace (using 3.2), a new C++
managed project, imported only the .cpp/.h-files, entered the properties
(there are some libraries necessary) and had a full reproduction of the
error-message. But the program started without problems and I can debug
it. What more could I change to get rid of the problem?
Do you think, only the message is broken, so I should deactivate it and
only take account of the console output? What do you mean with "build or
workspace question" - is "cdt" the wrong group?
Am I the only one, who is struck by this problem? :o(
|
|
|
| Re: Debug doesn't start: Errors exist in a required project [message #155630 is a reply to message #155614] |
Tue, 04 October 2005 01:04 |
| Eclipse User |
|
|
|
Originally posted by: mikhailkhod.rogers.com
>What do you mean with "build or workspace question" - is "cdt" the wrong
group?
No, the "cdt" is the right group, but the subject of your message is wrong.
As you see now the debugger has nothing to do with this problem. I am not an
expert in the build-related issues, to answer to your questions I need at
least a reproducible case. But if you change the subject and repost your
message it may attract the attention of the build specialists.
"Edzard Egberts" <e.egberts@tantec.de> wrote in message
news:dhs1t5$hem$1@news.eclipse.org...
> > This is a bug in the Eclipse platform. Unfortunately, it prevents to
start
> > the debugger if there is bug in your project. It has been fixed for the
> > Eclipse 3.2, but for some reason didn't make in Eclipse 3.1.1.
>
> Yes, I tried 3.2M2 and it started debugging after showing the message.
> That was not quite the thing I anticipated. :o(
>
> > So, the only way to get around it is to find out why Eclipse "thinks"
that
> > your project contains errors. This is more a build or workspace
question.
>
> There are 18 projects (and 4 librarie projects) and every single one
> seems to contain the error. I have not the faintest idea, for which kind
> of error I should look. It's an error Eclipse 3.0 only shows after a
> clean build - so that doesn't seem to be a constant error in my
> projects, because it changed depending to sequence of starting debug.
>
> For one project I just made a new workspace (using 3.2), a new C++
> managed project, imported only the .cpp/.h-files, entered the properties
> (there are some libraries necessary) and had a full reproduction of the
> error-message. But the program started without problems and I can debug
> it. What more could I change to get rid of the problem?
> Do you think, only the message is broken, so I should deactivate it and
> only take account of the console output? What do you mean with "build or
> workspace question" - is "cdt" the wrong group?
> Am I the only one, who is struck by this problem? :o(
>
|
|
| |
| Re: Debug doesn't start: Errors exist in a required project [message #155661 is a reply to message #155645] |
Tue, 04 October 2005 14:05 |
| Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
> can you give more details about any error markers in your projects? Like is
> there an error marker on the project even though there are no markers on any
> files?
Yes, I often noticed that and was wondering about. But normally I prefer
navigation-view, because I like the order of files better.
> Did you check the problems view?
No, I never took care of it (this seems to be an important part of the
problem - before the computer. ;o)
There had been three problems told for one projekt, I closed it and
after that I suddenly can debug all the other projects. After a clean
build of the failed project, there only was the following message in
"problems" remaining, but when doing my trick of changing source and
then start debug, all problems are gone:
Severity Description Resource In Folder Location Creation Time
2 make * CreateProcess((null), rm -rf ./Dlg_Liste.o ./Fl_Gruppe.o
../Fl_Table_Input.o ./Main.o ./dlg_bank.o ./dlg_eingabe.o ./dlg_kabine.o
../dlg_konfig.o ./dlg_kundenfenster.o ./dlg_meldung.o ./fl_bn_foto.o
../fl_bn_spender.o ./fld_bank.o ./fld_konfig.o ./t_client.o
../t_eingabepuffer.o ./Dlg_Liste.d ./Fl_Gruppe.d ./Fl_Table_Input.d
../Main.d ./dlg_bank.d ./dlg_eingabe.d ./dlg_kabine.d ./dlg_konfig.d
../dlg_kundenfenster.d ./dlg_meldung.d ./fl_bn_foto.d ./fl_bn_spender.d
../fld_bank.d ./fld_konfig.d ./t_client.d ./t_eingabepuffer.d
tt_Studio.exe, ...) failed. Das System kann die angegebene Datei
nicht finden. Fl_Kundenfenster line 0 4. Oktober 2005 15:07:47
(Translation of last sentence: "The system cannot find the specified file")
This is reproducible - "Clean" causes the problem, restart a smaller
build works. But I don't understand, which file is missing?
I tried again for an other project and it was the same. I tried a third,
smaller one without self made libraries and also something missing.
Making a new error in one project and starting an other one, now works -
I don't understand, why all the projects were blocked before.
Okay, this way I'm working for a year and the biggest part of my problem
suddenly is gone - seemed it had been a problem of updating. Finally (I
tried four or five times) Eclipse 3.1 now is working for me. But I would
be fond to get rid of this last problem, because it was one of the main
reasons, for my interest in updating.
Best regards,
Ed
|
|
|
| Re: Debug doesn't start: Errors exist in a required project [message #155737 is a reply to message #155661] |
Wed, 05 October 2005 06:20 |
 Norbert Plött
Messages: 233
Registered: July 2009 |
Senior Member |
|
|
Hmm...
This is all pretty confusing but my google research indicates that the
original error message is from make and says that make cannot find rm.exe
which it needs for the clean step of a full build. This is reported as a
problem and therefore your projects have an error marker when they are fully
rebuilt.
An incremental build has no clean step, does not try to call rm.exe and
therefore does not have any problems to report. So ...
1) Do you have rm? If you don't, get it :-)
2) Does this explain your problems?
Greets
Norbert
"Edzard Egberts" <e.egberts@tantec.de> schrieb im Newsbeitrag
news:dhu27o$8v3$1@news.eclipse.org...
>
>> can you give more details about any error markers in your projects? Like
>> is there an error marker on the project even though there are no markers
>> on any files?
>
> Yes, I often noticed that and was wondering about. But normally I prefer
> navigation-view, because I like the order of files better.
>
>> Did you check the problems view?
>
> No, I never took care of it (this seems to be an important part of the
> problem - before the computer. ;o)
> There had been three problems told for one projekt, I closed it and after
> that I suddenly can debug all the other projects. After a clean build of
> the failed project, there only was the following message in "problems"
> remaining, but when doing my trick of changing source and then start
> debug, all problems are gone:
>
> Severity Description Resource In Folder Location Creation Time
> 2 make * CreateProcess((null), rm -rf ./Dlg_Liste.o ./Fl_Gruppe.o
> ./Fl_Table_Input.o ./Main.o ./dlg_bank.o ./dlg_eingabe.o ./dlg_kabine.o
> ./dlg_konfig.o ./dlg_kundenfenster.o ./dlg_meldung.o ./fl_bn_foto.o
> ./fl_bn_spender.o ./fld_bank.o ./fld_konfig.o ./t_client.o
> ./t_eingabepuffer.o ./Dlg_Liste.d ./Fl_Gruppe.d ./Fl_Table_Input.d
> ./Main.d ./dlg_bank.d ./dlg_eingabe.d ./dlg_kabine.d ./dlg_konfig.d
> ./dlg_kundenfenster.d ./dlg_meldung.d ./fl_bn_foto.d ./fl_bn_spender.d
> ./fld_bank.d ./fld_konfig.d ./t_client.d ./t_eingabepuffer.d
> tt_Studio.exe, ...) failed. Das System kann die angegebene Datei nicht
> finden. Fl_Kundenfenster line 0 4. Oktober 2005 15:07:47
> (Translation of last sentence: "The system cannot find the specified
> file")
>
> This is reproducible - "Clean" causes the problem, restart a smaller build
> works. But I don't understand, which file is missing?
> I tried again for an other project and it was the same. I tried a third,
> smaller one without self made libraries and also something missing.
> Making a new error in one project and starting an other one, now works - I
> don't understand, why all the projects were blocked before.
>
> Okay, this way I'm working for a year and the biggest part of my problem
> suddenly is gone - seemed it had been a problem of updating. Finally (I
> tried four or five times) Eclipse 3.1 now is working for me. But I would
> be fond to get rid of this last problem, because it was one of the main
> reasons, for my interest in updating.
>
> Best regards,
>
> Ed
|
|
|
| Re: Debug doesn't start: Errors exist in a required project [message #155752 is a reply to message #155737] |
Wed, 05 October 2005 08:59 |
| Eclipse User |
|
|
|
Originally posted by: e.egberts.tantec.de
> 1) Do you have rm? If you don't, get it :-)
Oh, oh - I have MSYS, but it was not in the path.
> 2) Does this explain your problems?
Yes, now it works. :o)
It's always the same, when problems continue, I'm looking at the wrong
place for them - I thought of eclipse or my projects, but I never would
have thought of GNU-Tools. ;o(
Lots of thanks,
Ed
|
|
|
Goto Forum:
Current Time: Fri Apr 26 04:28:30 GMT 2024
Powered by FUDForum. Page generated in 0.04096 seconds |
] 
Search
Help
Register
Login
Home
