Hi, When I excecute the following command line wine --winver nt40 --dll shlwapi=b --managed -- /nfs2/bin/Xilinx/ise4.1i/bin/nt/par.exe -pl 5 -rl 5 -e 1 -t 1 -w /tmp/design.ncd design.ncd design.pcf the following error message is returned err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x400a5648 but if I run the following command line wine --winver nt40 --dll shlwapi=b --managed -- /nfs2/bin/Xilinx/ise4.1i/bin/nt/par.exe -pl 5 -rl 5 -w /tmp/design.ncd design.ncd design.pcf everything works fine! Does enyone now what the problem is? I'm using Redhat 7.1 with 2.4.12 kernel -- Patrik Eriksson | patrik.eriksson@netinsight.net Net Insight AB | phone: +46 8 685 04 89 V?stberga All? 9 | fax: +46 8 685 04 20 SE-126 30 STOCKHOLM, Sweden | http://www.netinsight.net
Patrik Eriksson <patrik.eriksson@netinsight.net> wrote: : Hi, : When I excecute the following command line : wine --winver nt40 --dll shlwapi=b --managed -- : /nfs2/bin/Xilinx/ise4.1i/bin/nt/par.exe -pl 5 -rl 5 -e 1 -t 1 -w : /tmp/design.ncd design.ncd design.pcf : the following error message is returned : err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 : addr 0x400a5648 Set up the wine debugger and look with "bt" in what sequence of calls that happens. : but if I run the following command line : wine --winver nt40 --dll shlwapi=b --managed -- : /nfs2/bin/Xilinx/ise4.1i/bin/nt/par.exe -pl 5 -rl 5 -w /tmp/design.ncd : design.ncd design.pcf : everything works fine! : Does enyone now what the problem is? Also try to use real dos pathes (e.g. c:/tmp/design.ncd ) in the arguments for the window programs. The application may have a look at them and may get confused. Bye -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Maybe Matching Threads
- : GLIM PROBLEMS
- Less aggressive on the first allocation of CSR if detecting an early exit
- Less aggressive on the first allocation of CSR if detecting an early exit
- Less aggressive on the first allocation of CSR if detecting an early exit
- Can I improve the efficiency of my scan() command?