>>>>> "Nick" == Nick Roberts <[EMAIL PROTECTED]> writes:
Nick>
Nick> I can suggest two workarounds:
Nick>
Nick> 1) Specify the core file later:
Nick>
Nick> Run gdb (like this): gdb --annotate=3 emacs
Nick>
Nick> Then in the GUD buffer:
Nick>
Nick> (gdb) core ~/emacs/src/core.3491
Nick>
Nick> 2) Use 'M-x gdba', which should work how you want but won't give you
Nick> the old behaviour.
Yes both your 2 suggested methods work fine, but this doesn't look like
a consistent user interface.
Not sure what you mean with old behaviour. Should I see a difference (as
long I don't set gdb-many-windows) between "M-x gdb" and "M-x gdba". Both start
by printing "gdb -annotate=3 <image-name>" and then give me a gdb and a source
window.
Isn't that confusing for the user when "gdb -annotate=3 <image-name> core"
works in one case, but not the other?
BTW when I strip "source " from the filename by adding:
(if (and file (string-match "^source " file))
(setq file (replace-match "" t t file)))
to the beginning gud-find-file, I can call gdb the usual way, i.e. with
<image> and core like I would do in the shell.
I also have serious performance issues with the new gdb interface, e.g.
gdb --fullname <image-name> core
and then "up" or "bt" in gdb takes a bit more than 20 seconds, whereas
gdba -annotate=3 <image-name> core
and then "up" or "bt" needs 2 and a half minutes.
This is almost certainly not an emacs problem, but seems to be caused by
the --annotate=3 option for gdb and of course our image size (125 MB and
155 for the core file).
Does "--annotate" even make sense when analyzing a core?
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: [EMAIL PROTECTED] |
------------------------------------------
---
The purpose of a windowing system is to put some amusing
fluff around your one almighty emacs window.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
