| Summary: | close(-1) segfaults on mips64 systems | ||
|---|---|---|---|
| Product: | uClibc | Reporter: | |
| Component: | stdio | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | uclibc-cvs |
| Priority: | P5 | ||
| Version: | 0.9.33.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
does it only segfault under qemu ? or does it crash on native hardware ? the close() code is a pure syscall to the kernel, so i can't see how it'd be crashing inside of uClibc. I don't see how this would crash in uClibc, so i suppose you meanwhile fixed this on mips for good.
open("/dev/nul", O_RDWR) = -1 ENOENT (No such file or directory)
close(-1) = -1 EBADF (Bad file descriptor)
exit_group(0) = ?
|
Hi, following test code segfaults on mips64 systems: qemu-system-mips64, big endian, n64 lemote yeelong, little endian,n32 #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <unistd.h> int main() { int n; n=open("/dev/nul", O_RDWR); close(n); return(0); } I don't know how to debug this further. Thanks for any hints. best regards Waldemar