On Thu, Jan 27, 2005 at 07:11:04AM -0500, John Weiss wrote: > On Tue, Jan 25, 2005 at 02:38:54PM +0000, Angus Leeming wrote: > > > > Which means that it's dead easy to set a break point in gdb. Any entry > > into lyxbreaker is automatically invalid, so stop there and have a look at > > the execution path to that point. > > > > Try it yourself: > > gdb ./lyx > > (gdb) break lyxbreaker > > Breakpoint 1 at 0x120132a34: file ostream, line 193. > > (gdb) run > > Ok, time for another language lesson: > > While, "break" means set a breakpoint to most of us comp.sci. types, > in common English, it can mean "smash with a hammer into little > inoperable bits". When you add the "-er" suffix, however, only the > latter meaning remains. That is, a "Zbreaker" would be someone who > rips apart "Z" so that it's now broken.
That's exactly what the lyxbreaker does. Once you call it, LyX will go down. > In short: calling a function "lyxbreaker" is a Bad Idea, as it > implies that this function somehow damages LyX. Well, it won't exactly hurt yiur installation, but as far as the running instance is concerned, one can hardly damage it any further. > Better to call it "lyxstopper" or "lyxbreakpt", the latter being far > more descriptive if its purpose. Maybe for native speakers. Me richst it full come when I white what meant it. Andre'
