On Tue, 2009-12-01 at 10:36 +0100, Øyvind Harboe wrote: > >> > No one was talking about linking with GDB. That's just insane. ;) > >> > libbfd is part of binutils. But again it should be_optional. > >> > >> OK. Explain the benefit of complicating OpenOCD vs. adding a script > >> to launch OpenOCD via GDB then... > > > > Seriously... you've never had a Heisenbug either? Am I the only one > > that gets segfaults and doesn't _want_ to have to debug them? Really? > > You're not answering the question:
You're not seeing my point. > How is your solution better than writing a script "openocd" that launches > openocd from GDB by default? You want to _force_ me to _always_ run GDB, to catch random segfaults? If you agree that such would be _unreasonable_ to ask, then when I get a segfault out-of-the-blue after working interactively, you expect me to reproduce it? What if I can't? And you could ask *users* to do that, and keep a straight face? The very notion should cause embarrassment. We have seen reports from users where the last line is "Segmentation Fault" and that's all they did. Your theory about asking people to do extra work has been shown to be ineffective at best, and it's downright annoying to consider the lack of respect that excluding this type of feature shows our _users_. > This script could run a bt automatically and create a "bug" file. To boot > we could add a circular debug_level 3 memory buffer that is dumped > at the same time... > > In releases we could default to running without gdb/debug_level 3 all the > time. How is this better than built-in, automatic stack traces? Exactly? I have code that works, adds value, and I will address and shortcomings regarding portability and selectability. Now, show me your solution. The burden is on _you_ to explain how your solution is better, because I do not buy the crap you guys are slinging tonight. I have explained repeatedly and clearly how this will benefit _users_, and it's really irritating me to see resistance to this idea -- when I bet most of you haven't even tried my patches yet. Please tell me (justly) I'm wrong. --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
