[Info-vax] Home-grown application process dumps

[VAXman- at SendSpamHere.ORG]

In article <d3fc58d6-fe56-4104-9aa4-f319f4ac6e6a at googlegroups.com>, mcleanjoh at gmail.com writes:
>From your ANALYZE/PROCESS_DUMP (???)
>
>%BAS-F-MEMMANVIO, Memory management violation=20
>-BAS-I-USEPC_PSL, at user PC=3D84236620, PSL=3D0000001B=20
>-SYSTEM-F-ACCVIO, access violation, reason mask=3D04, virtual address=3D000=
>00000002D=20
>0002, PC=3DFFFFFFFF84236620, PS=3D0000001B=20
>
>You're at PC 84236620 ?  That's way up high.  Is it in VMS code or dynamic =
>memory?  SDA might help tell you, assuming you have time to get into it and=
> do a SHOW PROCESS/IMAGE before the crash.
>
>Steve says that the 0002D0002 looks like a descriptor, so an attempted pass=
> by value rather than pass by reference (i.e. address) seems likely.
>
>Have you got some diagnostics in the code that help you identify how far it=
> got and hopefully help you pin down if not the line then at least the regi=
>on?  (I'm well aware that adding diagnostics can hide problems, especially =
>memory corruptions that now take place on memory that you don't access agai=
>n and therefore there's no problem, but it is worth a try.)


$ analyze/system
SDA> read/exec
SDA> examine 84236620

Does it detail were that PC is located?

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.