Hi all,
Can anyone help me with the following dilema:
I have been provided with a 3rd party threaded library (say libfoo.a)
believed to be stable, it has been in use for a few years and noone has
complained about
it cra****ng.
The program seems to run fine.
//pseudo c-code
main()
{
statement_a;
statement_b;
call_to_function_in_lib_foo();
statement_c;
statement_d;
}
I want to run this in the debugger and experiment with some variations
in statement_c or d
BUT when I run the code in the debugger (gdb) the program generates a
segment fault in call_to_function_in_lib_foo (after spawing some
threads) but before ever executing anything on
statement_c;
If I run the program and attach the debugger to the running process,
the debugger notes that there are 6 threads active, but when I try to
debug entirely in the debugger, it only gets to 4 threads and then
seg-faults.
Any ideas why the program works but would fail in a debugger? and any
ideas on how to resolve this?
Is this a debugger issue? library issue? (using gdb 5.3.9)
Thanks in advance...
Doug
--
comp.lang.c.moderated - moderation address: clcm@[EMAIL PROTECTED]
-- you must
have an appropriate newsgroups line in your header for your mail to be
seen,
or the newsgroup name in square brackets in the subject line. Sorry.
