On Tue, 2011-05-10 at 17:33 +0200, Michael T wrote:
> Hello all,
>
> I was wondering if it is possible to improve the debugging information
> generated by gcc when resolving C macros? Just as an example, when I
> preprocessed the following C file:
>
Have you tried '-g3'?
R.
> "Michael" == Michael T writes:
Michael> I was wondering if it is possible to improve the debugging
Michael> information generated by gcc when resolving C macros?
It could be done, but nobody has tried.
Michael> I wonder whether this couldn't be done by the gcc preprocessor?
Michael> Or do
> From: rasel...@hotmail.com
> > From: bas...@starynkevitch.net
> > On Tue, 10 May 2011 17:33:57 +0200
> > Michael T wrote:
> > > I was wondering if it is possible to improve the debugging information
> > > generated by gcc when resolving C macros? Just as an example, when I
> > > preprocessed the
> From: bas...@starynkevitch.net
> On Tue, 10 May 2011 17:33:57 +0200
> Michael T wrote:
> > I was wondering if it is possible to improve the debugging information
> > generated by gcc when resolving C macros? Just as an example, when I
> > preprocessed the following C file:
[...]
> I am not a st
On Tue, 10 May 2011 17:33:57 +0200
Michael T wrote:
> I was wondering if it is possible to improve the debugging information
> generated by gcc when resolving C macros? Just as an example, when I
> preprocessed the following C file:
>
> extern int printf (__const char *__restrict __format, ...);
Hello all,
I was wondering if it is possible to improve the debugging information
generated by gcc when resolving C macros? Just as an example, when I
preprocessed the following C file:
extern int printf (__const char *__restrict __format, ...);
#define my_macro(i) \
do { \
*(i) = 1; \
