| debugging under linux (fc5) [message #167253] |
Mon, 03 April 2006 17:31  |
Eclipse User |
|
|
|
Hi all,
I can't start the debugger in a simple helloworld app. As soon as I
start the debugger it greets me with the following:
Stopped due to shared library event
Stopped due to shared library event
mi_cmd_stack_list_frames: No stack.
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
kill
I haven't touched debugging directives, it is set by default to use
gdb local, configuration is debug. I searched a little and on windows
problem has to do with setting PATH entries etc, but I didn't find a
solution for linux.
|
|
|
|
|
|
| Re: debugging under linux (fc5) [message #167448 is a reply to message #167321] |
Wed, 05 April 2006 09:53  |
| Eclipse User |
|
|
|
There are no white spaces in the path(s) anywhere, gdb is in
/usr/bin/gdb and workspace in /home/boban/workpsace.
At first I was getting bunch of "Cannot access memory at address 0x0"
even though there couldn't have been any NULL pointer errors - program
was simply doing a printf. I changed the source later (testing
autocomplete mostly) and now I only get these funny messages.
FWIW, cdt & eclipse make a great C++ ide. I used to use Anjuta but I
think I'll switch to eclipse, even with "funny messages".
arne anka wrote:
>> Stopped due to shared library event
>> Stopped due to shared library event
>
> i get those as well, but am not sure whether they are _error_messages at
> all.
>
>> mi_cmd_stack_list_frames: No stack.
>
> have a look at http://marblemice.com/content/view/66/30/. does it fix
> the problem?
> if so there should be a bug-report -- eclipse has to escape the
> whitespaces before giving the path to gdb, imo.
|
|
|
Powered by
FUDForum. Page generated in 0.52046 seconds
Home