This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
What is the error? 'remote_exec host' has been used in some places in gdb >testsuite so it should work well. The one-line statement below works with >combinations of {remote-host, local-host} x {babeltrace installed, >babeltrace not installed}ERROR: tcl error sourcing ../../../gdb/gdb/testsuite/gdb.trace/ctf.exp. ERROR: bad spawn_id (process died earlier?)
This is what I got.
I think you get an error in this line remote_exec host "babeltrace $ctfdir < /dev/null" "" "" "output"
> > set ctfdir "foo" > set status [remote_exec host "babeltrace $ctfdir < /dev/null"] > verbose -log "status\[0\] ([lindex $status 0])" > verbose -log "status\[1\] ([lindex $status 1])" > >1) babeltrace installed (local-host and remote-host). We'll get, >status[0] (1) >status[1] ([error] opening trace "foo" for reading. > >2) babeltrace not installed, local-host. We'll get, >status[0] (-1) >status[1] (spawn failed) > >3) babeltrace not installed, remote-host. We'll get, >status[0] (1) >status[1] (sh: babeltrace: command not found) > >We can match 'status[1]' to know the different results of executing >'babeltrace' on host. > >P.S. I am not good at tcl/expect, so I may miss something.Thanks. I am very clear about this way. Do you mind I keep current way that I just used?
-- Yao (éå)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |