Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.pascal.delphi.misc > #417

Re: Jump to hex address

From Peter Fast <peter-not@newsgroups.only>
Newsgroups comp.lang.pascal.delphi.misc
Subject Re: Jump to hex address
Date 2012-11-17 12:41 +0200
Organization -
Message-ID <k87pj7$a73$1@speranza.aioe.org> (permalink)
References <1d659e14-a397-4a84-874f-2463dc60f983@uk1g2000pbb.googlegroups.com>

Show all headers | View raw


Brian wrote:
> 
> Access violation at address 00503D57 in module "SuchandSuch.exe". Read
> of address 0x00000004
> 
> Can I jump to this location in the source code in the debugger?
> 0x00503D57

That "SuchandSuch.exe" probably is the name of your own application?

If the address lies within your own code, or within your components 
there you also have source code, then you can use Search -> Find error 
and you can easily jump to that address in your source code.

If the address lies within Windows DLL files, you are out of luck.

Most often when I face errors that are ourside my scope are in some way 
related to Windows Printer Driver problems. The error may even pop up 
sometime after using some erroneous or non-compatible Printer driver.

The second most common error lies within my own code. That error address 
does not reveal the exact place what causes the error. But debugging 
line by line, I can trace the problematic line that makes Windows DLL 
error to appear, and I can fix it or go around it.

Occasional errors, errors that appear only about once a week or two and 
only at the customer's site, they are the most difficult to locate.
-PF

Back to comp.lang.pascal.delphi.misc | Previous | NextPrevious in thread | Find similar


Thread

Jump to hex address Brian <brian@brie.com> - 2012-11-16 14:37 -0800
  Re: Jump to hex address Peter Fast <peter-not@newsgroups.only> - 2012-11-17 12:41 +0200

csiph-web