This is the mail archive of the gdb@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]

Re: Huge problems with debugging threaded C++ programs


On Thu, May 23, 2002 at 03:38:16PM +0200, Carlo Wood wrote:
> 
> Let me state (again, but in more detail) what is the issue:
> 
> I run into gdb bugs very often, but can't make simple test
> cases for them - and thus never reported any of them.
> 
> I think that the only way for you to reproduce the problems
> is to install the same development environment as I have
> and simply reproduce the exact same situation.
> 
> My proposal is that you will install this environment; I will
> then commit my work the cvs repository of my project using
> incremental tags for every problem I run into, and mail you
> the tag and how to reproduce the problem.
> 
> The problems that I posted before can not be reproduced because
> I did not add tags thus far.
> 
> I propose you first put some time into installing the whole
> developing environment that I am working with.
> 
> In order to do this you will need a i686 running linux.
> (I am using an Athlon, but I think any i686 will do).
> 
> I am using kernel 2.4.18; I am not sure things will be too
> different if you'd use a 2.5 kernel, or a 2.2 kernel - but
> you could try just using what you have.  A difference might
> be caused by the fact that I am currently testing threaded
> applications and every tiny little change has effect on
> the program flow.
> 
> I am using RedHat here, and thus use rpms.  I have installed the
> glibc-2.2.4-19.3 rpm, but I am afraid I compiled it myself.
> Perhaps I should send you my rpm so you will be sure that
> your glibs is the same.  As far as I remember, the only
> difference is that I enabled debugging (so I can use gdb
> to trace into libc) and that I have the source code installed
> for that purpose.

What version of Red Hat Linux?

> Having the source code installed for glibc is important I am
> afraid (at least, for me, to find bugs in libcwd).
> 
> Finally, you should install the project that I am working on:
> 
> cvs -d:pserver:anonymous@cvs.libcwd.sourceforge.net:/cvsroot/libcwd login
> 
> (press enter on the password prompt)
> 
> cvs -z3 -d:pserver:anonymous@cvs.libcwd.sourceforge.net:/cvsroot/libcwd co libcwd
> 
> cd libcwd
> ./bootstrap
> 
> 'bootstrap' will probably flood you with demands to install things
> and/or upgrade things; please follow the instructions.
> 
> Finally you should have installed the release version of gcc-3.0.4
> and the corresponding g++.  You can install those seperately
> (not as default compiler).  If you don't have this installed already
> or know how to do it quickly then please tell me and I'll send you
> two scripts that makes installing new compiler versions very easy
> (I am using 11 different versions at the same time).
> 
> Please read the INSTALL file of the libcwd project for detailed
> information about what you need to install to compile things, to
> run ./bootstrap but also in order to run the testsuite.
> Probably you won't need to be able to run the testsuite in order
> to reproduce the problems that I am running into though.
> 
> Let me know if there are any problems.

None so far..

> 
> -- 
> Carlo Wood <carlo@alinoe.com>
> 
> PS I did not 'cvs commit' the most recent changes yet.

-- 
Liam Stewart :: Red Hat Canada, Ltd. :: liams@redhat.com


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