On 2006-11-14, Steve Underwood <[email protected]> wrote:
> Interesting. I always run msp430-gdbproxy from the command line, so it
> always runs in its own group. Thus, I would never have seen that. Are
> you sure this is new behaviour? I haven't changed anything about the way
> the program is run in recent versions.
I think it's due to the fact that I have to start the newer
version in a pipeline to filter out the debug messages. Here's
the shell script I use to start gdb:
------------------------------------------------------------
#!/bin/bash
killall msp430-gdbproxy
echo "starting msp430-gdbproxy..."
(setsid msp430-gdbproxy msp430 2>&1 | grep -v '^debug:') &
# msp430-gdbproxy msp430&
sleep 0.2
echo "starting gdb..."
msp430-gdb
killall msp430-gdbproxy
------------------------------------------------------------
If I remove the "setsid" from the pipeline, it will fail. But,
if I use the commented out line instead, it's fine.
Does gdbproxy only call setsid() if stdout/stederr is a tty?
--
Grant Edwards grante Yow! Yow! Am I in
at Milwaukee?
visi.com
