Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Where is the CDT error log located
Where is the CDT error log located [message #171281] Tue, 13 June 2006 01:47 Go to next message
Eclipse UserFriend
Originally posted by: smurli.starentnetworks.com

Hi,

I updated CDT to 3.1.0.200605290500 (RC2)
When i open a C file it says "An error had occured. See error log for more
details"

Can any one please tell me how do i get this error log, so that i could post
it to concerned person.

Thanks in Advance,
-Murli
Re: Where is the CDT error log located [message #171310 is a reply to message #171281] Tue, 13 June 2006 09:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ed_06.tantec.de

> I updated CDT to 3.1.0.200605290500 (RC2)
> When i open a C file it says "An error had occured. See error log for more
> details"
>
> Can any one please tell me how do i get this error log, so that i could post
> it to concerned person.

I think it's in workspace -> directory ".metadata" the file ".log"
Re: Where is the CDT error log located [message #171342 is a reply to message #171310] Tue, 13 June 2006 16:02 Go to previous message
Eclipse UserFriend
Originally posted by: newsgroups.snipah.com

Edzard Egberts wrote:
>
>> I updated CDT to 3.1.0.200605290500 (RC2)
>> When i open a C file it says "An error had occured. See error log for
>> more details"
>>
>> Can any one please tell me how do i get this error log, so that i
>> could post it to concerned person.
>
> I think it's in workspace -> directory ".metadata" the file ".log"

You can also use the Error Log view in Eclipse:
Window->Show View->Other->PDE Runtime->Error Log

Enrico
Previous Topic:Loading debug symbols for external shared libraries?
Next Topic:Customize representation of variables during debugging
Goto Forum:
  


Current Time: Sat Jun 07 19:28:45 EDT 2025

Powered by FUDForum. Page generated in 0.05635 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top