This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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]

How to get i386-vxWorks target's task entry point when Using gdb?


    I am trying to use gdb5.0 to remote debug i386-vxworks target's program.Gdb5.0 communicates with vxWorks's WDB agent,after patched by the file "gdb-5.0-wdbpatch-1.1".The patch comes from 
http://www.slac.stanford.edu/~strauman/gdb/index.html.
    Gdb works fine on starting up,connecting to wdb agent,reading file's symbols(using "file" command),setting breakpoints,etc.But I find when I use "run function_name" command to use gdb to spawn a task on vxWorks target via WDB agent,the task can be successfully created,but its entry point is 0x0 or some error value.Thus,when gdb resume the task after creating it,there immediately occurs an "PC counter"error on the target.It seems gdb calculate an wrong entry point when createing the task via WDB agent 's WDB_CONTEXT_CREATE interface before.
    I know on the target,we can use symFindByName to get the address of application _functionname to subsequenly spawn. Gdb5.0 uses file command to read in a.out format module's symbols,but why it canot get the right entry point?how to solve it?
    Thanks,
    Lize,Wang


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