Jump to content

Image of the Day

What's the best way to move your heavy stuff? Using a power loader! #spacr #screenshotsaturday 💪🤖💪 https://t.co/sOjz2XNVeq
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net's newsletters to receive the latest updates and exclusive content.


Sign up now

Debugger problem (SOLVED)

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
1 reply to this topic

#1 gbadebo   Members   

124
Like
0Likes
Like

Posted 26 January 2013 - 05:31 AM

hello, I have got problems using the debugger on eclipse, coding JAVA ...Android development. It is rather taking me backwards than being a useful tool for debugging I set break points. click debug then its jumps to a line I never specified -Debug Current Instruction Pointer (DCIP). Fine maybe its trying to tell me something useful here... but it never does and it doesn't allow me to get anything useful as it is stuck there and when i press resume ... it sticks to the same line. Sometimes when i exit eclipse and start again it temporarily dissapears but only for a nanosecond When i really really force it , sometimes a "class file editor" pops up saying "source not found", the rest - i cannot make a any sense of it. Was is this "debug current instruction pointer " for ? certainly i'm missing something here ... so how is this thing useful? How deos it help? and most importantly.... HOW CAN I REMOVE IT PERMANENTLY? I cant get any useful/crash debug info out of "DCIP" so far. when you are spending serious time trying to debug yr debugger then you are really going backwards. many thanks all help appreciated PROBLEM IS FINALLY SOLVED, THANKS


Edited by jbadams, 27 January 2013 - 05:41 AM.
Restored post contents from history.


#2 swiftcoder   Senior Moderators   

18034
Like
0Likes
Like

Posted 26 January 2013 - 10:21 AM

Please don't delete post contents, or mark threads as solved. We prefer to leave threads intact so that others can learn from them.


Tristam MacDonald - Software Engineer @ Amazon - [swiftcoding] [GitHub]





Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.