Hi,
Thanks
for your inputs. Also, is there a way in Eclipse to find debug information
about the programs?
In
continuation with below mail, I would like to provide a snapshot of the errors
which I can observe on Eclipse console once I enable tracing while debug:
====================================================================
Launching
test application: data/launch/bin/MultiThread.exe
====================================================================
266,627
[MI] 1-inferior-tty-set /dev/pts/17
266,731
[MI] 1^done
266,743
[MI] (gdb)
266,787
[MI] 2source .gdbinit
266,806
[MI] &"source .gdbinit\n"
266,806
[MI] &".gdbinit: No such file or directory.\n"
266,806
[MI] 2^error,msg=".gdbinit: No such file or directory."
266,806
[MI] (gdb)
266,814
[MI] 3-gdb-set auto-solib-add on
266,832
[MI] 3^done
266,832
[MI] (gdb)
266,837
[MI] 4-environment-directory
266,838
[MI] 4^done,source-path="$cdir:$cwd"
266,841
[MI] (gdb)
266,841
[MI] 5-break-insert -t main
266,842
[MI] &"No symbol table is loaded. Use the
\"file\" command.\n"
266,843
[MI] 5^error,msg="No symbol table is loaded. Use the
\"file\" command."
266,855
[MI] (gdb)
!ENTRY
org.eclipse.cdt.dsf 4 10005 2010-03-05 11:54:26.856
!MESSAGE
Request for monitor: 'RequestMonitor
(org.eclipse.cdt.dsf.concurrent.RequestMonitorWithProgress@6bf15d27): Status
ERROR: org.eclipse.cdt.dsf.gdb code=10004 Failed to execute MI command:
-break-insert
-t main
Error
message from debugger back end:
No
symbol table is loaded. Use the "file" command.
java.lang.Exception: No symbol table is loaded. Use the "file"
command.' resulted in an error.
!SUBENTRY
1 org.eclipse.cdt.dsf.gdb 4 10004 2010-03-05 11:54:26.857
!MESSAGE
Failed to execute MI command:
-break-insert
-t main
Error
message from debugger back end:
No
symbol table is loaded. Use the "file" command.
!STACK
0
java.lang.Exception:
No symbol table is loaded. Use the "file" command.
at
org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:806)
at
org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:645)
This
error is repeated for most of the tests.
As
seen in the above trace, error related to .gdbinit file are logged.
I
have kept the .gdbinit file in my home directory.
I
have also updated the PATH variable with the path of gdb binary.
I
am currently trying to execute Test suite for 6.8.
I
have executed all steps as mentioned in the following link before executing
JUnit tests.
http://wiki.eclipse.org/CDT/cdt-debug-dsf-gdb#Launching_the_tests
I
am not sure if I have missed any steps.
If
anybody has any suggestions/comments, kindly let me know.
Sneha
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of John Cortell
Sent: Thursday, March 04, 2010 6:13 PM
To: CDT General developers list.; cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Problem with executing dsf-gdb JUnit tests
It sounds like the test programs lack debug information.
Those programs are built by the Eclipse dsf-gdb test plugin--it runs a script
that invokes makefiles.
The first thing I would do is use the readelf (specify -w) to see
if the binaries have debug info. If they don't then examine how the programs
are being built; something unexpected might be going on there. If they do have
debug information, then something else is going wrong.
John
At 05:33 AM 3/4/2010, sneha_apte wrote:
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_14B8F27D7CE40C4C9E481B2B845C2E0D037312CFC0EXCHANGEpersi_"
Hi all,
I am trying to execute JUnit tests for dsf-gdb from Eclipse. However I am
getting following type of error for most of the tests:
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2010-03-04 15:46:17.832
!MESSAGE Failed to execute MI command:
-break-insert -t main
Error message from debugger back end:
No symbol table is loaded. Use the "file" command.
!STACK 0
java.lang.Exception: No symbol table is loaded. Use the "file"
command.
at
org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:806)
at
org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:645)
I am performing following steps:
1. Checked out cdt-all, dsf, dsf-gdb plugins from CVS HEAD.
2. Pre-requisite of the tests is that the gdb binary should have given names:
- gdb.6.6
- gdb.6.7
- gdb.6.8
- gdb.7.0
3. As per post from following link, test cases for gdb 6.8
are all passing.
http://old.nabble.com/DSF-GDB-JUnit-tests-td27533144.html
4. On my machine, the gdb binary is named "gdb" only. It is of 6.8
version.
5. Thus I added a link gdb.6.8 pointing to this gdb.
6. I have also included the path to this symbolic link in the PATH variable.
Some more information:
7. I am using eclipse Helios.
8. Number of tests to be executed is displayed as 136.
If anybody can provide me some pointers / guidance it would be of great help.
Thanks and Regards,
Sneha
DISCLAIMER ========== This e-mail may contain privileged and confidential
information which is the property of Persistent Systems Ltd. It is intended
only for the use of the individual or entity to which it is addressed. If you
are not the intended recipient, you are not authorized to read, retain, copy,
print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message.
Persistent Systems Ltd. does not accept any liability for virus infected mails.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.