On Wed, May 16, 2012 at 3:56 PM, Manuel López-Ibáñez <lopeziba...@gmail.com> wrote: > On 16 May 2012 15:40, Richard Guenther <richard.guent...@gmail.com> wrote: >>> >>> Without that patch displaying happen too late (and eats a lot of Emacs >>> CPU)!! >> >> 1) Fix emacs (do not buffer stderr) >> 2) do not omit -quiet when running from inside emacs > > Actually, I wonder how you (Richard) and other GCC hackers work with > and debug GCC, because it is a real pain in the ass. > > * All the TREE_ macros don't work.
I have memoized all sub-fields of tree, so I don't use those macros (still other people use them with some gdbinit macdefs and -g3). > * __extension__ prevents GDB from evaluating many things. I did not run into this one yet - maybe open a GDB bug? > * announce_function dumps slow down Emacs (and the shell when working > via SSH) when debugging anything related to libstdc++ (or any large > testcase). I always use -quiet, even when debugging. I do not use -quite when tracking down compile-time hog issues. > * Hitting auto-completion in GDB means staring at the window for 5-10 > minutes until it decides to stop listing stuff. That works for me. Though my debug-cc1 is built with a C compiler (yes, with C++ this will get a pain in the ass ...) > There are quite a few other annoyances, but these are the most common > (perhaps I should make a list in the wiki). The most common annoyance for me is stepping into trivial inline functions when trying to step into an "important function", thus foo (tree_code_length (x), a, b); something people want to make even more prominent :( Richard. > Cheers, > > Manuel.
