Hi
  I was wondering if someone might be able to help me regarding some problems that I am having with vxgdb (vxWorks gdb) and the gcc cross-compiler.  I am using the gcc compiler version 3.0.2 and the vxgdb version 4.13.  The vxgdb version is probably quite old now(??), but it worked fine with gcc version 1.39 ( I know pretty old too!!!!).  I will look into building a more up to date vxgdb, but just in case there is an extra flag or something else that I can try, I thought that I would ask the question first.  I built the cross-compiler 3.0.2 with the following flags:-

./configure --with-gnu-as --with-gnu-ld --enable-languages=c --target=m68k-wrs-vxworks  
  --with-headers=/S765AT/auto/third_party/vxworks/vw5.1.1/vw/h

This built fine and appears to work fine.

My Problem
==========
The code that is being debugged is being generated and so to some extent is not in normal format, but that is not really the issue.  The main problem is that my system is designed to set break points on lines like (of which there may be many instances of in a file):-

{ __analog_shell_debug_variable;}

where _analog_shell_debug_variable is declared as

static volatile char _analog_shell_debug_variable = '\0';

If I compile this with the older version of the compiler it always happily sets break points.  However if I compile it with the new version of the compiler it does not always find the line in the source......I get errors like:-

break t1.c:22
No source file named t1.c                                                                      which I find very worrying...the file does exist!!!!!

or

No line 61 in file "t1.c"

where line 61 is { __analog_shell_debug_variable;}.

I have tried -g, -g1, -g2 etc with the same results.  I realise that the { __analog_shell_debug_variable;} is doing nothing and that maybe the compiler is compiling it out. In fact if I change it to something like { int i = __analog_shell_debug_variable;} it seems to fix this problem.

However is there any better method...compiler flags for example that I could try.  I also sometimes get a problem after I have set a break point, in that when I try and run to it, it seems to think that its running to a break point in a different file???  But most of the time it seems to work.  However is there any known problems regarding 3.0.2 and gdb.  Should I rebuild a new version of vxgdb?

I have attached some vxgdb output when I attempt to set break points that do not work  at all.

Thanks for your help. If I need to give more info, then please let me know.

  Phil Prentice