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 |
Brad Noyes <maitre at ccs.neu.edu> writes: > >I'm writing a c++ program that before i changed distributions from >RH6.0, to Mandrake worked. But now i try to run it i get a >Segmentation fault when i execute it with no core dump. Is there >anyway that i can figure out why it is seg faulting with gdb, or >something? I expect a shared library on Mandrake is incompatible with the corresponding one on RH6.0 (even though that isn't supposed to happen). Try recompiling. If that doesn't help, then run it under gdb. I also suggest you look at electric-fence or yamd, which use the virtual memory hardware to help debug memory access bugs. >And why wouldn't this seg fault yield a core dump? I can usually tell >what is wrong when there's a core dump. Maybe the default max core size is smaller on the Mandrake system. Check the ulimit command (a bash builtin). - Jim Van Zandt - 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. |