Michael Schwingen a écrit : > Michel Catudal wrote: > >> ECDT_Debugger_Name = gdb >> >>>> >>>> >>>> >>> This is a silly default, but there isn't really a good default here. >>> I chose arm-elf-gdb. >>> >>> >>> >>> >> It is easy to change, I was just mentionning that it looks bad because >> gdb is the local debugger and not an embedded one. >> A common free debugger is arm-elf-gdb while the most familiar commercial >> versions have eabi in it. It would be better to have arm-elf-gdb >> or arm-linux-gdb since if you forget to change the default you will not >> get weird messages that will confuse the hell out of a newbie. >> A missing filename message is better than a criptic message which unless >> you realize that it is trying to debug x86 stuff makes no sense. >> >> > This is just silly. > > You have to change it anyway - *any* default will be wrong for a > majority of users. > > On my work machine, I have these versions: > /opt/cgdb/bin/powerpc-eabi-gdb > /opt/cgdb/bin/sh-elf-gdb > /opt/gdb-6.3/bin/powerpc-eabi-gdb > /opt/gdb-6.5/bin/powerpc-eabi-gdb > /opt/gdb-6.7.1/bin/arm-elf-gdb > /opt/gdb-6.7.1/bin/powerpc-eabi-gdb > /opt/gdb-6.7.1/bin/sh-elf-gdb > /opt/gdb-6.8/bin/arm-elf-gdb > /opt/gdb-6.8/bin/powerpc-eabi-gdb > > which are used for different projects. Whichever is the default is wrong > for most work, and if the default is any one of these instead of the > native gdb, it won't help a bit for any debugging work that requires a > different one. > > cu > Michael >
You misunderstood my comment. I've had to explain to many people why they had such a ridiculous message. If you forget to change a name that doesn't exist you are likely to find a problem much quicker than if you get an error message that on the surface appeared to be legitimate. I too have several different version, actually a few more than you. Most people using free software do not as they stick usually to one. I was pointing out a way to make it easier to find such silly error. I've had people searching for a long time as to why they could not get their debugger to work, perhaps they thought that the plugin was able to sniff the debugger as codeblocks do. The solution would be to either make sure that the default debugger is not the system debugger or do as codeblocks does and make it possible to identify the debugger correctly. Michel -- Tired of Microsoft's rebootive multitasking? then it's time to upgrade to Linux. http://home.comcast.net/~mcatudal _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
