[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Issue with -gdb-set stop-on-solib-events with Eclipse
|
From what I have seen, CDI (which you are using) is
using the "Stop on shared lib event" to properly deal with breakpoints that
are
set in libraries that are not loaded yet. So, my
guess is that when you turn off that option, CDI will actually leave it on but
will
automatically resume the program to make it look to the
user like it is doing the right thing.
You could use DSF-GDB which never stops on library
events. However, unless you use HEAD, we don't handle
breakpoints
in library that are not loaded. Depends on what
you really need.
Marc
Hi guys,
I am using Eclipse with GDB 6.8 on Linux (Ubuntu
9.04). Before debugging any C program, in the Debugger tab -> Shared
Library, I uncheck "Stop on shared library event". But check "Load shared
library automatically". However, when I start debugging using verbose console
mode, I see that the "Stop on shared library event" is set to off and then on
again. This is inspite of me unchecking "Stop on shared library event" in the
Debug Configuration.
This setting is causing problems for me, since Eclipse
hangs sometimes during debugging. I want the autoloading of shared libraries
to be on but not the second option. I have come across some posts with such a
problem. But there is no solution mentioned.
I tried unchecking both, but
then my program does not work in that case. GDB terminates before debugging
starts.
I tried the same options from command line i.e.(Autoloading on but
stop of shared library event off) and everything works properly. Is there any
solution to this ?
--
Thanks & Regards,
Rohit
Girme
