working c program dies in gdb

[doug]

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 crashing.

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 from the command line outside the debugger
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 on why the program would work normally but fail when run 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

[Richard Heathfield]

doug said:

<snip>

Any ideas on why the program would work normally but fail when run in a
debugger?

Yes. The program is exhibiting undefined behaviour. That is, it contains a
bug.

and any ideas on how to resolve this?

Fix the bug.

Is this a debugger issue? library issue? (using gdb 5.3.9)

Programmer issue.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at the above domain, - www.

[Yingjian Zhan]

I don't see ur exact code. here is my guess.
maybe you pass local variables to the thread creation functions. If you are
lucky enough the program can run without crashing at some chances.
but if you use a debugger things r different because the execution sequence
changed.
Just a guess. you can use bt to find out what you passed to the library
routine. Be sure they are independent to the execution sequence of threads.
BR

"doug" <db*******@yahoo.comwrote in message
news:11**********************@p59g2000hsd.googlegr oups.com...

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 crashing.

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 from the command line outside the debugger
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 on why the program would work normally but fail when run 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