step-by-step degugging goes on different path than a normal execution

Bug #529289 reported by Ofni Chadesch
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdbg (Ubuntu)

Bug Description

Binary package hint: kdbg

I don't know if this is a kdbg related bug, or there is something related with my program. Please bear with me. It seems that when I open a file it goes all well and nice on the actual execution, while an inspection of the code throws a failure.
To help you replicate this problem, I appended to this report the content of the c++ source code and I attached the text file.
Thank you for your time,

version: kdbg 2.2.0 3.5.10, Kubuntu (karmic) 4:3.5.10.dfsg.1-2ubuntu7.2
(this is not the package from ubuntu repositories,
but the one form kdbg website .deb package thanks to Ana Beatriz Guerrero Lopez)
OS: Linux (x86_64) release 2.6.31-19-generic (Kubuntu Karmic 9.10)
Compiler: Target: x86_64-linux-gnu

--asdf.cpp(the source file)-------------
#include <fstream>
#include <iostream>
#include <string>
using namespace std;

int main (){
  string data="input test";
  ifstream infile;
  cout << "Reading from the file" << endl;;
  throw ios_base::failure::failure("");
getline(infile, data);
  getline(infile, data);
  cout << data << endl;}
return 0;}
I compiled this file using the following command:
g++ -Wall -Wextra -pedantic -g -o run asdf.cpp
(version information g++ (Ubuntu 4.4.1-4ubuntu9) 4.4.1)
Thank you again, hope to hear from you soon.

Revision history for this message
Ofni Chadesch (ulawe) wrote :
Revision history for this message
Ofni Chadesch (ulawe) wrote :

Surprisingly when I use gdb it doesn't have this problem, so the failure is confined to kdbg.
GNU gdb (GDB) 7.0-ubuntu configured as "x86_64-linux-gnu"

Ofni Chadesch (ulawe)
Changed in kdbg (Ubuntu):
assignee: nobody → Ofni Chadesch (ulawe)
assignee: Ofni Chadesch (ulawe) → nobody
Revision history for this message
Ofni Chadesch (ulawe) wrote :

I can't believe in five year no one even acknowledged this bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers