On Sáb, 2013-01-26 at 13:13 +, Sérgio Basto wrote:
> On Qua, 2013-01-16 at 15:36 +0100, Jakub Jelinek wrote:
> > On Wed, Jan 16, 2013 at 02:26:00PM +0100, Jan Kratochvil wrote:
> > > On Wed, 16 Jan 2013 04:12:29 +0100, xning wrote:
> > > > Shall we should modify '-g' to '-g3' to have gcc save
On Qua, 2013-01-16 at 15:36 +0100, Jakub Jelinek wrote:
> On Wed, Jan 16, 2013 at 02:26:00PM +0100, Jan Kratochvil wrote:
> > On Wed, 16 Jan 2013 04:12:29 +0100, xning wrote:
> > > Shall we should modify '-g' to '-g3' to have gcc save the macro
> > > info? So when we install *-debuginfo packages,
Hello xining,
xning a écrit:
> Shall we should modify '-g' to '-g3' to have gcc save the macro info?
> So when we install *-debuginfo packages, we can look up a macro
> definition, just like we can look up a function definition.
For what it's worth, I believe that would be useful, yes. Though
On Wed, Jan 16, 2013 at 02:26:00PM +0100, Jan Kratochvil wrote:
> On Wed, 16 Jan 2013 04:12:29 +0100, xning wrote:
> > Shall we should modify '-g' to '-g3' to have gcc save the macro
> > info? So when we install *-debuginfo packages, we can look up a
> > macro definition, just like we can look up a
On Wed, 16 Jan 2013 04:12:29 +0100, xning wrote:
> Shall we should modify '-g' to '-g3' to have gcc save the macro
> info? So when we install *-debuginfo packages, we can look up a
> macro definition, just like we can look up a function definition.
That would be great, I have not found any officia
Hi guys,
Shall we should modify '-g' to '-g3' to have gcc save the macro info? So
when we install *-debuginfo packages, we can look up a macro definition,
just like we can look up a function definition.
The gdb info says,
GDB knows about preprocessor macros and can show you their expansio
