|
From: <ar...@de...> - 2004-02-05 07:28:53
|
I wouldn't have filed it as a valgrind bug if I hadn't checked out the possibility of a GDB bug first... when not run under valgrind, termios_p is not NULL. The instruction which generated SIGSEGV under valgrind completes successfully. It's the first call from set_tty_state in GDB to tcsetattr, and the third call to tcsetattr in the program. The version of GDB (6.0-4) in Debian unstable should reproduce this. Jeremy Fitzhardinge <je...@go...> writes: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > You reported the bug, or are watching the reporter. > You are on the CC list for the bug, or are watching someone who is. > > http://bugs.kde.org/show_bug.cgi?id=74016 > je...@go... changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |INVALID > > > > ------- Additional Comments From je...@go... 2004-02-03 03:36 ------- > Yep. Your target program (gdb) touched a NULL pointer in __GI_tcsetattr, and suffered a SIGSEGV as a consequence - and Valgrind told you all about it. > > Now, why __GI_tcsetattr got a NULL pointer is another question. It might be a problem in Valgrind's emulation of something to do with terminals/job control. Or, more likely, there's a bug in your program. > > If it looks like a job control/signal bug in Valgrind, please file another bug. -- Andrés Roldán <ar...@de...> GPG Key-ID: 0xB29396EB http://people.fluidsignal.com/~aroldan |