Patrick Doyle [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
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)]
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
Hi,
I am also facing the same problem.
I am using RH 7.2 on IA32 box, with kernel 2.4.7-10.
U can reproduce (is it a bug) this as follows. Use the test case given below.
[root@nadda randd]# cat test.c
#include stdlib.h
int main(int argc, char **argv) {
char *p=getenv(MYTEST);
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
