> Hm, maybe this should be a FAQ. Both indicate that youre accessig > memory that you shouldn't. A segfault does. I did a quick check of the kernel (core kernel + arch/i386), and found two places where processes get SIGBUS: swapping out a process failing to free any memory (swap_out in mm/vmscan.c) the page fault handler failing to handle a fault because it's out of memory (do_page_fault in arch/i386/mm/fault.c). Other unixes probably do things differently. Jeff ************ [EMAIL PROTECTED] http://www.linuxchix.org
- [techtalk] printing images Raven Brooke
- [techtalk] gcc versions and bus error Becky L. Norum
- Re: [techtalk] gcc versions and bus error moebius
- Re: [techtalk] gcc versions and bus error Nicole Zimmerman
- Re: [techtalk] Update: gcc versions and bus erro... Becky L. Norum
- Re: [techtalk] gcc versions and bus error Laurel Fan
- Re: [techtalk] gcc versions and bus error Jeff Dike
- Re: [techtalk] gcc versions and bus error Robert Kiesling
- Re: [techtalk] Thanks: gcc versions and bus ... Becky L. Norum
- Re: [techtalk] gcc versions and bus error Robert Kiesling
- Re: [techtalk] printing images moebius
- Re: [techtalk] printing images Raven Brooke
- Re: [techtalk] printing images moebius
- Re: [techtalk] printing images Robert Kiesling
- Re: [techtalk] printing images Raven Brooke
- Re: [techtalk] printing images Robert Kiesling
- Re: [techtalk] printing ima... Raven Brooke