July 2002 - openSUSE Programming - openSUSE Mailing Lists

Re: [SLE] Debug C++
by Setyo Nugroho 08 Jul '02

08 Jul '02

Hi John, No, init.c is not mentioned anywhere in the program. Even for a simple prog like below, I cannot display (list) the prog using gdb. ---- #include <iostream> class CSegiempat { int lebar, tinggi; public: CSegiempat (int,int); int luas (void) {return (lebar*tinggi);} }; CSegiempat::CSegiempat(int a, int b) { lebar = a; tinggi = b; } int main () { CSegiempat persegi1 (3,4); CSegiempat persegi2 (5,6); cout<<"luas persegi1 = "<<persegi1.luas()<<endl; cout<<"luas persegi2 = "<<persegi2.luas()<<endl; } --------- regards Setyo > > Subject: Re: [SLE] Debug C++ > Date: Mon, 08 Jul 2002 18:14:36 +0000 > From: John Lamb <J.D.Lamb(a)btinternet.com> > To: Setyo Nugroho <snugroho(a)gmx.net> > Cc: suse-programming-e(a)suse.com > > Setyo Nugroho wrote: > > Hi all, > > I have a problem to debug my C++ program. The error msg in gdb: > > "init.c: No such file or directory." > > I am not sure, whether it has to do with the recently installed Suse 8. > 0? > > (1) Message should really be posted to suse-programming-e > > (2) Can you post a fragment of source code? Is "init.c" mentioned > anywhere in the source? > > JDL > > -- > > Non enim propter gloriam, diuicias aut honores pugnamus set propter > libertatem solummodo quam Nemo bonus nisi simul cum vita amittit. > > ------------------------------------------------------- > -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

2 1

Re: [SLE] Debug C++
by John Lamb 08 Jul '02

08 Jul '02

Setyo Nugroho wrote: > Hi all, > I have a problem to debug my C++ program. The error msg in gdb: > "init.c: No such file or directory." > I am not sure, whether it has to do with the recently installed Suse 8.0? (1) Message should really be posted to suse-programming-e (2) Can you post a fragment of source code? Is "init.c" mentioned anywhere in the source? JDL -- Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.

1 0

How to read /proc/xxx/mem file??
by Salman Khilji 08 Jul '02

08 Jul '02

Hi: I am writing an application that needs to read another process's memory without affecting the target processor whatsoever. This is different from a source line debugger that has to stop the application. Someone told me that on Solaris, you fopen /proc/<process-id> file, fseek to the correct offset, and then fread the required # of bytes. On Linux, things a different. There is not /proc/<process-id> file. Rather /proc/<process-id> is a directory in which you find a file named mem. If I cat this file for a process, I get nothing. Anyone got any idea how to read this file? I wrote this program, but it fails. I also heard (but did not confirm) that on Linux, you must first attach to the target process using the ptrace function. But doing so, stops the execution of the running process----I don't want that. This would be unacceptable. #include <stdio.h> #include <unistd.h> //#include <sys/ptrace.h> int main() { FILE* pFile; char buffer[4]; int temp; float value; pFile = fopen("/proc/1673/mem", "rb+"); if(pFile == 0) return -1; // I got the address of a global variable in the // process from objdump temp = fseek(pFile, 0x8050b50, SEEK_SET); // this call fails :-( temp = fread(buffer, 4, 1, pFile); value = *((float*)(buffer)); return 0; }

2 1

Fwd: Re: [suse-programming-e] post increment and self assignment problem
by Verdi March 06 Jul '02

06 Jul '02

John Lamb wrote: > I would avoid this kind of code in a real program because it's > inefficient, difficult to read, and there may be a danger that some agree 100%. > compiler will get it wrong. On the other hand, it's a good way to find > out how C++ works. well, that's what I'm doing now :D Regards, Verdi > JDL > > -- > > Non enim propter gloriam, diuicias aut honores pugnamus set propter > libertatem solummodo quam Nemo bonus nisi simul cum vita amittit. -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

1 0