Hi Cameron,
Ahh, very funny. A little Aussie humor there? Took me a second but I got
it ;-)
Bus error (core dumped)
Relax, your bus is fine. DX is definitely not behaving correctly with
multiprocessor script mode. If you built it with debug and can get a
decent core file, a printout of the stack might be helpful in debugging the
problem.
When you get the corefile, do a:
dbx <path-to-dxexec>/dxexec core
(dbx) where
(I have recollections of trying the same and not getting anything useful
but maybe yours will dump out closer to the problem. I also tried
purifying this a while back, but purify was too finicky to be helpful.)
Randy
Cameron Huddlestone-Holmes:
|Thanks Randall,
|
|
|Based on your suggestions I tried a few things - here are the results.
|hzslice is the name of my script.
|
|Starting with a command line "dx -processors 2 -memory 1024 -script"
|Then "dx>include hzslice"
|Everything works fine.
|
|Starting with a command line "dx -processors 1 -memory 1024 -script hzslice"
|Everything works fine.
|
|Starting with a command line "dx -processors 2 -memory 1024 -script hzslice"
|It stops before executing the sequencer (found that by using the Describe
|module as suggested).
|
|I get exactly the same behaviour using the sample script "Sequencer" now
|that I have tried it.
|
|Go figure? Runs much quicker with two processor, so if anyone know a fix I'd
|appreciate it. If not, is this the sought of thing I should stick in a bug
|report?
|
|Also, I have never had a problem with my Bus!
|
|Cheers,
|
|Cameron
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA N127-01; RTP, NC 27711
