execute test fails in gcc testsuite...

[Venkatesan Jeevanandam-2]

I am working on the testsuite for a new crosscompiler hosted on x86
Platform,

While performing execute test using gcc testsuite,

I am getting the error message in execute test
/tmp/20000112-1.x0: /tmp/20000112-1.x0: cannot execute binary file

I know, have to use cross compiler simulator, for executing
$Arch-sim /tmp/20000112-1.x0

But I don't know where to mention this configuration.

how can I pass the execute test because the target application only can run
under simulator, I'd also looked into the c-torture.exp under the lib dir of
the testsuite source, suppose it depend on the call to gcc-load(.....). But
still no hint to understand the syntax staff of expect. maybe I'm wrong
totally, thanks in advance for any suggestion.

Please help me.

--Venkat


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.
E-mail may contain viruses. Before opening attachments please check them for viruses and defects. While MindTree Consulting Limited (MindTree) has put in place checks to minimize the risks, MindTree will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside.


_______________________________________________
DejaGnu mailing list
DejaGnu@...
http://lists.gnu.org/mailman/listinfo/dejagnu

[Ben Elliston-37]

> I know, have to use cross compiler simulator, for executing
> $Arch-sim /tmp/20000112-1.x0
>
> But I don't know where to mention this configuration.

You do this through the board definition.  Can you send what you have
in your board .exp file to the list so that we can point out what's
wrong?

Ben


_______________________________________________
DejaGnu mailing list
DejaGnu@...
http://lists.gnu.org/mailman/listinfo/dejagnu

[malreddy]

Venkatesan Jeevanandam-2 wrote:

I am working on the testsuite for a new crosscompiler hosted on x86
Platform,

While performing execute test using gcc testsuite,

I am getting the error message in execute test
/tmp/20000112-1.x0: /tmp/20000112-1.x0: cannot execute binary file

I know, have to use cross compiler simulator, for executing
$Arch-sim /tmp/20000112-1.x0

But I don't know where to mention this configuration.

how can I pass the execute test because the target application only can run
under simulator, I'd also looked into the c-torture.exp under the lib dir of
the testsuite source, suppose it depend on the call to gcc-load(.....). But
still no hint to understand the syntax staff of expect. maybe I'm wrong
totally, thanks in advance for any suggestion.

Please help me.

--Venkat


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.
E-mail may contain viruses. Before opening attachments please check them for viruses and defects. While MindTree Consulting Limited (MindTree) has put in place checks to minimize the risks, MindTree will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside.


_______________________________________________
DejaGnu mailing list
[e-mail]
http://lists.gnu.org/mailman/listinfo/dejagnu

hi venkatesan,

Do u got the solution for excution test failures ,

IF u know the solution please let me know because i am getting execution failures

in libmudflap like this



Executing on host: /home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/g++ -B/home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/ -ggdb3 -DDEBUG_ASSERT -I../../../../libmudflap/testsuite -I../../../../libmudflap/testsuite/.. -I.. -I../../libstdc++-v3/include -L/.libs -Lsrc/.libs  -fmudflap -c -o ctors-1.o ../../../../libmudflap/testsuite/libmudflap.c++/ctors-1.cxx    (timeout = 3000)
../../../../libmudflap/testsuite/libmudflap.c++/ctors-1.cxx:22: warning: mudflap cannot track unknown size extern 'k'^M
a------------------------------------------------------a
output is ../../../../libmudflap/testsuite/libmudflap.c++/ctors-1.cxx:22: warning: mudflap cannot track unknown size extern 'k'^M
 
output is:
../../../../libmudflap/testsuite/libmudflap.c++/ctors-1.cxx:22: warning: mudflap cannot track unknown size extern 'k'^M
 
PASS: ctors-1 compilation
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
remote exec
Executing on host: /home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/g++ -B/home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/ -ggdb3 -DDEBUG_ASSERT -I../../../../libmudflap/testsuite -I../../../../libmudflap/testsuite/.. -I.. -I../../libstdc++-v3/include -L/.libs -Lsrc/.libs  -fmudflap -c -o ctors-2.o ../../../../libmudflap/testsuite/libmudflap.c++/ctors-2.cxx    (timeout = 3000)
a------------------------------------------------------a
output is
PASS: ctors-2 compilation
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
remote exec
Executing on host: /home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/g++ -B/home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/ -ggdb3 -DDEBUG_ASSERT -I../../../../libmudflap/testsuite -I../../../../libmudflap/testsuite/.. -I.. -I../../libstdc++-v3/include -L/.libs -Lsrc/.libs ctors-1.o ctors-2.o  -fmudflap -lmudflap -lstdc++  -L/testsuite -lm  -o ctors-12.exe    (timeout = 3000)
a------------------------------------------------------a
output is
PASS: ctors-12 linkage
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
call---------remote
remote exec
Executing on host: /home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/g++ -B/home/rpmuser/rpmdir/BUILD/gcc-4.1.2/objdir/gcc/ -ggdb3 -DDEBUG_ASSERT -I../../../../libmudflap/testsuite -I../../../../libmudflap/testsuite/.. -I.. -I../../libstdc++-v3/include -L/.libs -Lsrc/.libs ctors-2.o ctors-1.o  -fmudflap -lmudflap -lstdc++  -L/testsuite -lm  -o ctors-21.exe    (timeout = 3000)
a------------------------------------------------------a
output is
PASS: ctors-21 linkage
call---------remote
./ctors-12.exe: ./ctors-12.exe: cannot execute binary file^M
call---------remote
FAIL: ctors-12 execution
call---------remote
./ctors-21.exe: ./ctors-21.exe: cannot execute binary file^M
call---------remote
FAIL: ctors-21 execution