[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] No source file named x.cpp/no line xx in filex.cpp
|
It's hard to say. Try to set the "verbose console mode" option. You will see the CDT/gdb communication trace in the console view.
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of loeffler@xxxxxxxxxxx
Sent: 27 February 2007 14:31
To: cdt-debug-dev@xxxxxxxxxxx
Subject: RE: [cdt-debug-dev] No source file named x.cpp/no line xx in filex.cpp
I added the "-g" option to some of the Makefiles in my project which I am interested in debugging - I think the order of the option does'nt matter, right?
Noting changed, still same errmsg...
I wonder that the stacktrace in case of a crash shows the correct filename and lines?
Markus
Von: "Mikhail Khodjaiants" <Mikhail.Khodjaiants@xxxxxxx>
Datum: 26. Februar 2007 19:30:34 MEZ
An: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
Betreff: RE: [cdt-debug-dev] No source file named x.cpp/no line xx in filex.cpp Antwort an: CDT Debug developers list <cdt-debug-dev@xxxxxxxxxxx>
First of all, what is your environment? If it is Windows gdb doesn't handle this situation well.
If it is Linux there could be many reasons. First, make sure that all your libraries are built with the "-g" options.
"No source file named x.cpp" means that your library hasn't been loaded yet at the time when the debugger is trying to set a breakpoint. "no line xx in file x.cpp" could be a result of having two files with the same names in different directories, for example.
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Markus Löffler
Sent: 26 February 2007 18:07
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] No source file named x.cpp/no line xx in filex.cpp
ok, I have to check that (not in the office today and new to the
project)
But what can I do if so?
Am 26.02.2007 um 18:51 schrieb Mikhail Khodjaiants:
I suspect that's the problem. Does your project load the libraries dynamically?
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev- bounces@xxxxxxxxxxx] On Behalf Of Markus Löffler
Sent: 26 February 2007 17:23
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] No source file named x.cpp/no line xx in filex.cpp
Hi Mikhail,
no, all files are part of the project and all sources are present.
I have 1 master-project which has about 10 sub-projects which build seperate libs.
Best
Markus
Am 26.02.2007 um 18:05 schrieb Mikhail Khodjaiants:
Hi Markus,
Are you trying to set breakpoints in the files that are not a part of your project? If so, you have to change the source lookup path - see the Source tab of the launch configuration dialog.
Regards,
Mikhail
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev- bounces@xxxxxxxxxxx] On Behalf Of Markus Löffler
Sent: 26 February 2007 16:58
To: cdt-debug-dev@xxxxxxxxxxx
Subject: [cdt-debug-dev] No source file named x.cpp/no line xx in file x.cpp
Hi there,
I have a problem using the debugger. I'am working on a larger project (with "standard makefile") in a team under suse linux 10 with clearcase. No one else is using eclipse so I get no help from inside my team.
When I start the debugger I get many "No source file named x.cpp"
and "no line xx in file x.cpp" errmsg in the console - but not for all files in the project. Breakpoints in that files are ignored and the stack trace does not point to the right souce files.
Does anyone know how to fix that?
Best
Markus
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
