| Debugger Problem [message #150984] |
Wed, 10 August 2005 05:34  |
Eclipse User |
|
|
|
Originally posted by: stefanm.uniblue.net
Hi there,
I have a problem debugging my application. I found a related post here
(26.07. by Mark Fortner) that seems to describe something similar.
Environment:
------------
Eclipse v3.1 (Build ID - I20050513-1415)
CDT v3.0.0 RC3
Windows XP SP2
MinGW/GCC 3.4.2
Problem:
--------
.: I set a single breakpoint and begin debug process.
.: The debugger starts at main() and waits for input
.: Click on Resume to allow debugger to run to next breakpoint
.: Debugger halts on arbitrary position within a function
.: I get the following reference in the Debug view:
Thread[1](Suspended: Signal 'SIGSEGV' received. Description:
Segmentation
fault.
.: Any attempt to Step Over, Step In or Resume results in the debugger
to remain at the current position.
.: Trying a number of Step Over, Step In and Resume (does not matter
which
you press) the debugger will simply terminate gracefully.
This problem occured a number of times and seems to be shifting, giving
the impression of a linker fault. Sometimes it is resolved after modifying
the code....
Funny enough no problem is reported if the application is simply run and
not debugged...
I have a screenshot, but don't know how to attach it.
Also in amendment to aboves' post reference, the path of my project is
c:\eclipse\workspace\storage_tape_test and does not contain any spaces.
Any input helps,
Stefan
|
|
|
|
|
| Re: Debugger Problem [message #151041 is a reply to message #151010] |
Thu, 11 August 2005 04:23  |
| Eclipse User |
|
|
|
Originally posted by: stefanm.uniblue.net
Hi Mikhail,
it was a pointer issue. I guess I didn't see it because the code still
used to run (debug) on Borland. I had to port the code as Borland has
problems compiling templates. My guess is that Borland captures some of
those pointer issues and simply 'ignores' them... kind of like a safety
net.
I fixed the issue and it runs ok now.
Thanks
Mikhail Khodjaiants wrote:
> This means a memory violation happens during the execution of your program.
> Stepping further is meaningless, try to investigate the current state to
> find the corrupt pointer.
> "Stefan" <stefanm@uniblue.net> wrote in message
> news:fd3782bc02ce76efbef601ca49edf474$1@www.eclipse.org...
>> Hi there,
>>
>> I have a problem debugging my application. I found a related post here
>> (26.07. by Mark Fortner) that seems to describe something similar.
>>
>> Environment:
>> ------------
>> Eclipse v3.1 (Build ID - I20050513-1415)
>> CDT v3.0.0 RC3
>> Windows XP SP2
>> MinGW/GCC 3.4.2
>>
>> Problem:
>> --------
>> .: I set a single breakpoint and begin debug process.
>> .: The debugger starts at main() and waits for input
>> .: Click on Resume to allow debugger to run to next breakpoint
>> .: Debugger halts on arbitrary position within a function
>> .: I get the following reference in the Debug view:
>>
>> Thread[1](Suspended: Signal 'SIGSEGV' received. Description:
>> Segmentation
>> fault.
>>
>> .: Any attempt to Step Over, Step In or Resume results in the debugger
>> to remain at the current position.
>> .: Trying a number of Step Over, Step In and Resume (does not matter
>> which
>> you press) the debugger will simply terminate gracefully.
>>
>> This problem occured a number of times and seems to be shifting, giving
>> the impression of a linker fault. Sometimes it is resolved after modifying
>> the code....
>>
>> Funny enough no problem is reported if the application is simply run and
>> not debugged...
>>
>> I have a screenshot, but don't know how to attach it.
>>
>> Also in amendment to aboves' post reference, the path of my project is
>> c:eclipseworkspacestorage_tape_test and does not contain any spaces.
>>
>> Any input helps,
>>
>> Stefan
>>
|
|
|
Powered by
FUDForum. Page generated in 0.04697 seconds
Home