![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
OK, that makes sense. So let me ask, was it that the core dump wasn't created? Or that the core dump couldn't be written to disk becuase of user permissions? I would guess the latter was the case. Otherwise Mandrake isn't much use for programmers on a multi-user system (unless everyone has root, which is absurd). Scott Stirling West Newton, MA ----- Original Message ----- From: "Brad Noyes" <maitre at ccs.neu.edu> > Why didn't i get a core dump? Well i haven't been using Mandrake for very long, > only about a few weeks. I'm still getting used to it. I tried ulimit, and it > was set to unlimited. So that wasn't the problem. I then tried to run the > program as super user (by accident, i didn't realize i was in su). And then i > got a core dump, which made me happy. After a few tests I concluded that with > Mandrake, only root, or super user can create core dumps. > > I've head of security exploits using a core dump. So i guess thats why > Mandrake allows only root to create core dumps. > > Now i have to info to fix the problem I just have to figure out how to fix the > problem ... - 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).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |