Ian Hulin <[email protected]> writes: > Hi all, > This isn't an problem as regards en-users, but only occurs when running > LilyPond under gdb.
<URL:http://sourceware.org/bugzilla/show_bug.cgi?id=15415> > I'd like to collect information for any work-rounds people have employed > so we can document this in the CG. The only stuff we have about using > C++ debuggers is an old .gdbinit file from Han-Wen. David, Mike, Keith, > Phil it's obvious from your posts and patches that you're able to > massage gdb to get past this so you can do some *useful* debugging. > Could you guys let me know what you do in the way of setting things for > gdb so I can get a patch in to make sure it's in the CG. If something > about this is already in the CG, please point me to it so I maybe make > it easier to find for people on GNU development learning curve. ln -f lily/out/lilypond out/bin/lilypond Yes, this is stupid and fragile, and you need to repeat it after recompilation. Perhaps you want to add a comment to the above bug report that is being ignored to the degree of not getting assigned to anybody. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
