🚀 go-pugleaf

Hi,
I just want to gave a small test case for the problem reported by
Patrick.
My actual application is some thing different, however on the same
lines.
My application (it's a MT application) sets the LD_LIBRARY_PATH
(putenv(LD_LIBRARY_PATH)) from the executable path (i.e from argv[0])
and later part of the code uses the dlopen and creates threads.
Unfortunatly the dlopen is not able to see the change in the
LD_LIBRARY_PATH by the application. It only remembers the
LD_LIBRARY_PATH when it is execed. So i need to call the execvp with
the same application (by this time in my app, there won't be any
threads, except the main) somewhare between setting the path and
before using dlopen. And when i debug the application i am getting the
above mentioned error from gdb.
Cheers,
Srini



"Tauno Voipio" <tauno.voipio@iki.fi.SPAMBAIT_REMOVE> wrote in message news:<YXJn8.341$So2.49070@read2.inet.fi>...
> "Patrick Doyle" <doylep@eecg.toronto.edu> wrote in message
> news:699e3226.0203191209.403ad50e@posting.google.com...
> > Hi.  I hope this is helpful...
> >
> > When debugging a program that uses pthreads, a call to execv causes
> > gdb to get mighty confused:
> >
> > (gdb) run
> > Starting program: abc
> > [New Thread 1024 (LWP 8440)]
> > Breakpoint 2 (...)
> > 736             execvp(argv[0], argv);
> > (gdb) cont
> > Continuing.
> > Cannot find user-level thread for LWP 8445: generic error
> > (gdb) bt
> > Cannot find thread 1024: generic error
> > (gdb) quit
> > The program is running.  Exit anyway? (y or n) y
> > Cannot find thread 1024: generic error
> > (gdb) [5]   Terminated              gdb abc
> >
> > [6]+  Stopped                 gdb abc
> > [bash]$ kill %
> >
> > [6]+  Stopped                 gdb abc
> > [bash]$
> > [6]+  Terminated              gdb abc
> > [bash]$
> >
> > This is Red Hat 7.2 and GNU gdb 20020225.
> 
> Just wonder ...
> 
> What are you trying to achieve?
> You replace the whole executable (if the exec.. succeeds) and would like to
> get GDB keeping track of it. Besides, if there are other threads running,
> they may get confused by the sudden replacement of the whole process code.
> 
> Tauno Voipio
> tauno voipio @ iki fi