|
From: Julian S. <js...@ac...> - 2005-08-01 16:48:21
|
> >The stdout/stderr output panes give plain text only. They're envisaged use > > is as debugging aids, not as interactive shells. Perhaps one day, if > > there's enough people wanting this... > > Maybe lots of people just dont use the program because they see they cannot > use it ;) > As a workaround, maybe it can be set so the output of the program can be > redirected to the console the program is started in, so ncurses and ansi > color programs would work as expected. Yes, that's maybe a more robust/general solution. > The real problem here was not the ioctl, but the argument passing to the > program. valkyrie passes the whole "Binary flags" option as *one* parameter > to the program (one argv entry) which confuses getopt/getopt_long, so I got > " eth1" instead of "eth1" which of cause confuses the ioctl, since there > really is no such device... maybe this should be fixed to pass them the > same way the shell does ? I can half-see what you are saying, but it would help a lot if you could send a specific example of what flag(s) it is that Valkyrie is passing incorrectly to Valgrind. J |