gdb trace problem

gdb trace problem

[Shamile Khan]

Hi,

1) First, please note that I am only having this issue from
a linux terminal and not windows terminal. My target board
is connected to a Windows host running a gdb stub.
(Actually a Xilinx application called XMDStub). 

I connect to the target using remote tcp (my gdb on a host
communicates with the gdb stub). I am trying to get this to
work from a linux host running gdb and I am having
problems. I can connect to my target and run the
application but I cannot set breakpoints or step through
the code. I can put one breakpoint and I can reach there
but when I try to continue I get this message

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000000 in ?? ()

I would like to know why this is happening. Also I noticed
that when I connect to my target (using Linux) with the
command "target remote xxx:port executable.elf" command, I
get this reply back 

Remote debugging using xxx:port executable.elf
0x00000000 in ?? ()

From a windows host running gdb, doing the same thing shows
a non zero address. What is this address?? 

2) I have a question regarding cross-compilers and cross
debuggers. Does it matter for the debugger if my
application was compiled from windows for a ppc target
(cygwin-ppc cross compiler) or from linux for a ppc target
(linux-ppc cross compiler).   


Additional Information
--------------------
1) - My windows host runs a Xilinx supplied version of
Insight/gdb
- My Linux host runs the standard Insight/gdb downloaded
from Redhat site
- The target is connect to a Windows machine running a
Xilinx supplied gdb stub called XMD Stub

Is Its possible that the Xilinx supplied Insight has some
configuration settings that I should use for my Linux
version of insight.

Thanks,



__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com