Yes that is what I did; it (gdb) stopped reacting upon reproducing my crash (in nautilus) not upon attaching to the process. That's what I was trying to say above, but I case I wasn't clear enough. So again:
I attached gdb to the running nautilus, typed continue in gdb. Nautilus then worked fine. I then proceeded to reproduce my crash by navigating nautilus to the directory in question and copying the .svg file. At this point nautilus crashed (as it usually did for me, that is what the bug is about) but also gdb stopped reacting. No matter what I typed in gdb nothing at all happened. I hope this makes the problem clear. Thanks for the help. atreju -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/196996 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
