Segmentation fault (solved ... sort of)
maitre at ccs.neu.edu
Mon Feb 7 17:50:55 EST 2000
Here's some out put ...
[brad at jupiter prog]$ ls -al segfault.c
-rw-r--r-- 1 brad brad 60 Feb 7 17:49 segfault.c
[brad at jupiter prog]$ gcc segfault.c
[brad at jupiter prog]$ ./a.out
[brad at jupiter prog]$ su
[root at jupiter prog]# ./a.out
Aborted (core dumped)
[root at jupiter prog]# more segfault.c
int main(int argc, char *argv)
[root at jupiter prog]# cd ..
[root at jupiter brad]# ls -al -d prog
drwx------ 22 brad brad 1024 Feb 7 17:50 prog/
[root at jupiter brad]#
[root at jupiter prog]#
On Mon, 07 Feb 2000, Kevin D. Clark wrote:
> Brad Noyes writes:
> > Well i first thought that it was because of a permission issue, bu [BAD WRAP]
> > to write the object files, and the binary to that directory, and b [BAD WRAP]
> > looked at the permissions of the directory. And yes, that would make it tough
> > on developers.
> What does the following C program produce on your system?:
> int main(int argc, char *argv)
> return 0;
> BTW, this isn't a suid-root executable, is it?
> Kevin D. Clark | |
> kclark at NOSPAM.ctron.com | kdcNOSPAM at alumni.unh.edu | Give me a decent UNIX
> Cabletron Systems, Inc. | PGP Key Available | and I can move the world
> Durham, N.H. (USA) | |
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).
More information about the Discuss