| Subject: | issues with automatic gdb firing on segfault |
1) To start with, when the attempt to start getting gdb trace feature was added? I can't see it in Changes. I was caught by surprise. this bt etracting should be enabled by default, since it interferes w/o other setups which already try to do that. at least there should be a way to disable it. (remember the straps discussion, Andy?)
2) the core file is not always called core. Often (especially on linux) it's called core.$pid (e.g. core.12345), so when T-H now tries to run:
Executing /usr//bin/gdb "/home/stas/perl/5.8.6-ithread/bin/perl5.8.6" "core" (bt)...
[...]
/home/stas/apache.org/mp2-pool/core: No such file or directory.
3) as far as I remember Devel::CoreStack sucks, since it requires a manual involvement (e.g. paging of the screens in gdb). there is a much better module called Devel::GDB, e.g. see how it is used in Apache-Test/lib/Apache/TestReport.pm