This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bdm-devel] RE: Problems using Insight/GDB for Coldfire


On Thu, 2003-10-02 at 18:20, Paul Whitfield wrote:
> (gdb) target bdm /dev/bdmcf0
> Remote bdm connected to /dev/bdmcf0
>   Coldfire debug module version is 1 (5307/5407(e))
> 
> (gdb) tk gdb_target_has_execution
> 0

This is a problem. This indicates a problem with the target backend.
It's not setting the pid/ptid when the target is attached. See
src/gdb/gdbtk/generic/gdbtk-cmds.c:gdb_target_has_execution_command.

Normally, one of the target vector commands will set ptid (or pid for
older versions of gdb) to non-zero -- typically 42000 or some other
"significant" number.

If you have the source code for the backend, check that something in the
target vector sets the ptid on attach. (See, for example, monitor_open
in monitor.c, which sets "inferior_pid = pid_to_ptid (42000);".

Keith



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]