← Back to team overview

touch-packages team mailing list archive

[Bug 662693] Re: gdb doesn't return the prompt after "next" instruction while debugging code using boost

 

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/662693

Title:
  gdb doesn't return the prompt after "next" instruction while debugging
  code using boost

Status in “gdb” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gdb

  On ubuntu 10.10, gdb 7.2-1ubuntu2, debugging a program that use
  boost::asio (libboost 1.40.0-6ubuntu1) .

  It worked perfectly before upgrading to 10.10.

  if I set a breakpoint and then try to issue a "next" gdb doesn't get
  to the prompt. It just sit here

  #0  epoll_wait() at :0
  #1  boost::asio::detail::epoll_reactor<false>::run() at /usr/include/boost/asio/detail/epoll_reactor.hpp:470
  #2  boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::do_one() at /usr/include/boost/asio/detail/task_io_service.hpp:260
  #3  boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::run() at /usr/include/boost/asio/detail/task_io_service.hpp:103
  #4  run() at /usr/include/boost/asio/impl/io_service.ipp:58
  #5  pion::PionScheduler::processServiceWork() at PionScheduler.cpp:118
  #6  thread_proxy() at :0
  #7  start_thread() at :0
  #8  clone() at :0
  #9  ??() at :0

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