Re: [Openocd-development] 0.1.0 release segfaulting during gdb sessions

Please provide a stacktrace according to the instructions at the bottom: http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html __

Re: [Openocd-development] Naming convention of *.cfg files

Hi all, I have updated the config file naming convention according to all the suggestions. Is this better? Regards, Pieter Index: openocd.texi === --- openocd.texi(revision 1399) +++ openocd.texi(working copy) @@ -3

Re: [Openocd-development] Naming convention of *.cfg files

On Mar 5, 2009, at 8:03 PM, Duane Ellis wrote: Pieter Conradie wrote> [many rules for config names] +Rule 1: [no spaces, use underlines] Agreed. I would add *all* non-ascii problematic chars become underline too, or are removed. ie: What about a name like: "O'Conner Chips Are Us" Techn

Re: [Openocd-development] Naming convention of *.cfg files

Pieter Conradie wrote> [many rules for config names] > +Rule 1: [no spaces, use underlines] Agreed. I would add *all* non-ascii problematic chars become underline too, or are removed. ie: What about a name like: "O'Conner Chips Are Us" > +Rule 2: [mfg prefix] Agreed. > +Rule 3: The name used mu

[Openocd-development] 0.1.0 release segfaulting during gdb sessions

I'm trying to use openocd to do remote gdb debugging on a AT91SAM7 board. It definitely works but after stepping for a little while the openocd process always segfaults. I'm very new to openocd but I suspect it shouldn't crash like this. I'm having trouble running openocd under gdb or I woul

Re: [Openocd-development] Naming convention of *.cfg files

On Thu, Mar 5, 2009 at 8:49 PM, Dean Glazeski wrote: > I agree.  Keep the configuration files in all lowercase.  It leads to much > less confusion and less of a likelihood of problems in Linux land due to > case problems. Another approach would be if all target config files had a displayname. T

Re: [Openocd-development] Naming convention of *.cfg files

I agree. Keep the configuration files in all lowercase. It leads to much less confusion and less of a likelihood of problems in Linux land due to case problems. I'm also wondering if the manufacturer of a target controller or board is necessary at the beginning of the configuration file. After

Re: [Openocd-development] Naming convention of *.cfg files

Laurent Gauch wrote: > For me it will be better to remove uppercase for any files. > Me too! > /target/atmel_at91sam7s.cfg not /target/Atmel_AT91SAM7S.cfg > /board/atmel_at91sam7s-ek.cfg not /board/Atmel_AT91SAM7S-EK.cfg > > I would like that ALL openocd source files use 'abcdef' but not 'Abc

Re: [Openocd-development] Naming convention of *.cfg files

On Mar 5, 2009, at 6:33 AM, Laurent Gauch wrote: Hi Øyvind and list members, I have taken artistic liberty to create the first draft of the Config file (*.cfg) naming convention. I guess that it is now open to debate. Over to you... Best regards, Pieter Index: openocd.texi

[Openocd-development] Naming convention of *.cfg files

> > Hi Øyvind and list members, > > I have taken artistic liberty to create the first draft of the Config file > (*.cfg) naming convention. I guess that it is now open to debate. Over to > you... > > Best regards, > Pieter > > Index: openocd.texi >

Re: [Openocd-development] Naming convention of *.cfg files

What's a manufacturer? That's not obvious when PCB & CPU differs. -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html ___ Openocd-development mailing list Openo

Re: [Openocd-development] Naming convention of *.cfg files

Hi Øyvind and list members, I have taken artistic liberty to create the first draft of the Config file (*.cfg) naming convention. I guess that it is now open to debate. Over to you... Best regards, Pieter Index: openocd.texi === --