← Back to team overview

touch-packages team mailing list archive

[Bug 1202220] Re: step function does not work with gdb-mutiarch

 

closing this rather old issue. sorry for not addressing this earlier.
Please could you recheck with the recent 14.04 LTS or 14.10 releases and
reopen the issue if the problem persists?

** Changed in: gdb (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1202220

Title:
  step function does not work with gdb-mutiarch

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  In cross mode, running gdbserver from 12.04 armhf in the target and
  using gdb-multiarch in the host 12.04 x86 ubuntu, we can connect to
  the target using suitable gdbinit file but we cannot use step command
  in gdb-mutliarch shell. Using once starts the program to be run in the
  gdbserver, using it once more the program completion in the target.

  Steps to repro:
  Test C file: test.c

  #include <stdio.h>

  void printest()
  {
  printf("printest function.\n");
  printf("printest function.\n");
  printf("printest function.\n");
  printf("printest function.\n");
  }

  int main(int argc, char *argv[])
  {

  printf("Hello World!\n");
  printf("Hello World!\n");
  printest();
  printest();
  printf("Hello World!\n");
  printf("Hello World!\n");
  return 0;
  }

  Build:
  arm-linux-gnueabihf-gcc -g test.c -o test

  In target:
  gdbserver :1234 ./test

  In host:
  gdb-multiarch ./test

  gdbinit file used has:
  set solib-absolute-prefix <path of targetfs used in ARM target> 
  set sysroot <path of targetfs used in ARM target> 
  set solib-search-path <path of targetfs used in ARM target> /lib:<path of targetfs used in ARM target> /usr/lib
  set architecture arm

  In the gdb shell:
  (gdb)target remote <ip>:1234 
  (gdb) step
  (gdb) step

  Output:
  The program terminates in the target and the debugging is stopped.

  Also, I verified that using just the latest 12.04-armhf gdb (not the
  client/server combination) in the target itself that the same issue
  does not reproduce.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1202220/+subscriptions