avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-libc-dev] SIGNAL / INTERRUPT checking


From: Colin O'Flynn
Subject: Re: [avr-libc-dev] SIGNAL / INTERRUPT checking
Date: Fri, 27 Feb 2004 17:49:44 +0000
User-agent: KMail/1.5.3

Hi,

Thought of another idea.

Search the input files for the SIGNAL() or INTERRUPT() macro, and get the 
interrupt name (BTW are SIGNAL() and INTERRUPT() case sensitive?), then 
search the output file for them. If it finds any it means they were not 
converted... also search for any SIG_ for good luck (to catch anything else). 
This way for most you can get line information to report back.

Just working on the prototype now so testing out different ideas...

  -Colin


On February 27, 2004 04:37 pm, E. Weddington wrote:
> On 27 Feb 2004 at 15:50, Joerg Wunsch wrote:
> > As Colin O'Flynn wrote:
> > > Would there be any interest in a program to check for legal SIGNAL /
> > > INTERRUPT names?
> >
> > Something like:
> >
> > sigcheck: $(TARGET).elf
> >  nm $(TARGET).elf | grep SIG_ >/dev/null && \
> >  echo "Warning: it is likely that there are misspelled SIG_* names"
> >
> > ?
> >
> > :-)
> >
> > Normally, all SIG_* names are supposed to be resolved into _vector_N
> > names by the preprocessor magic.  So if any SIG_ survived into the
> > output symbol table, that is most likely the programmer's fault.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]