On Mon, Oct 02, 2006 at 11:19:11AM -0400, Camm Maguire wrote:
>Greetings, and thanks for looking into this! It is still there on the
>sid dchroot on vaughan:
>
>camm@vaughan:~$ cat t.c
>int
>main(int argc,char * argv[]) {return system(argv[1]);}
>camm@vaughan:~$ cc -g t.c -o t
>camm@vaughan:~$ ./t "echo g"
>g
>camm@vaughan:~$ cc -g -pg t.c -o t
>camm@vaughan:~$ ./t "echo g"
>
>
>
>[1]+ Stopped ./t "echo g"
>camm@vaughan:~$ camm@vaughan:~$ kill %1
>
>
>[1]+ Stopped ./t "echo g"
>camm@vaughan:~$ [1]+ Terminated ./t "echo g"
>camm@vaughan:~$ gdb ./t
Hmmm. I suspect that this might even be a problem with vaughan rather
than libc. I just logged in to check on this, and did a chroot
unstable. Then:
93sam@vaughan:~$ cp ~camm/t.c .
Segmentation fault
I can't reproduce that again, now, but...
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"Since phone messaging became popular, the young generation has lost the
ability to read or write anything that is longer than one hundred and sixty
characters." -- Ignatios Souvatzis
Attachment:
signature.asc
Description: Digital signature