RE: GDB issues on Trunk

["Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>]

>-----Original Message-----
>From: Andrew Pinski [mailto:pinskia@gmail.com]
>Sent: Saturday, August 25, 2012 1:31 PM
>To: Iyer, Balaji V
>Cc: gcc@gcc.gnu.org
>Subject: Re: GDB issues on Trunk
>
>On Sat, Aug 25, 2012 at 10:28 AM, Iyer, Balaji V <balaji.v.iyer@intel.com> wrote:
>> Hello Everyone,
>>         I am trying to debug "cc1" through gdb but is not working as it was before
>(my current revision is 190623) . For example, when I try to print out any local
>variable when I am inside the function, it says the variable is not in in the context.
>Here is an example below:
>
>What version of gdb are you using?  IIRC for the trunk at least GDB
>7.5 is required now to debug code generated from it as we produce some
>dwarf4 that only 7.5 and above understands.

Yes, upgrading to gdb 7.5 seem to have fixed the problem! I was using 7.4.1 and 7.2 in my machines.

Thanks,

Balaji V. Iyer.


>
>Thanks,
>Andrew
>
>>
>> e.g.
>>
>> Single stepping until exit from function _ZL14tree_vectorizev, which
>> has no line number information.
>> vectorize_loops() () at ../../trunk-gcc/gcc/tree-vectorizer.c:168
>> 168       unsigned int num_vectorized_loops = 0;
>> (gdb) n
>> 173       vect_loops_num = number_of_loops ();
>> (gdb) p num_vectorized_loops
>> No symbol "num_vectorized_loops" in current context.
>>
>>
>> Another wierd thing I noticed is that "Breakpoint 1 and Breakpoint 2" generally
>point to 2 lines in diagnostic.c (I believe they are fancy_abort and internal_error)
>but now it is just giving addresses. Also, when I start something, it says it can't
>find line number information:
>>
>> Can someone please tell me how I can to fix these?
>>
>> Any help is greatly appreciated!
>>
>> Thanks,
>>
>> Balaji V. Iyer.
>>
>> PS. Please CC me when responding.