Anonymous_User Absent Member.
Absent Member.
845 views

Good article on how to read coredump or use debugger

Hi Guys,

Anyone know a good article to use debugger commands to indentify which
process and threads causing abend and hopefully which function.


Or does anyone has a sample steps ?

I got a coredump file, I can open it, but have limited commands that I
know.


regards,


nsrdman
Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Good article on how to read coredump or use debugger

On Mon, 27 Feb 2006 16:40:31 -0800, <nsrdman@hotmail.com> wrote:

> Hi Guys,
>
> Anyone know a good article to use debugger commands to indentify which
> process and threads causing abend and hopefully which function.
>


There have been some brainshare sessions about coredumps, but they handed
out cheat sheets without having anything in the session papers.

>
> Or does anyone has a sample steps ?
>
> I got a coredump file, I can open it, but have limited commands that I
> know.


The most important commands most of the time are '?' to display where you
are, 'ds/dds/sw' to display the stack, and 'r' to show the registers and
current instruction. Oh, and the '.m' command to get get module
information. The commands I've listed produce information that is often in
the abend log, as well, although '?' may provide more detail than
"server.exe + 378900" (to make up an example). '-a' should produce an
abend log.

If the version of vdb you have supports it, '-ldb' to extract the logger
screen messages.

For specific cases, other commands are likely to be useful, but predicting
which commands is a bit of an art -- it depends on where the problem is,
and is apt to be version dependent and knowing what you're looking at.
Usually some choice of dump command ('d' or 'dd' with an address argument)
would be the next step, and doing an 'lo' to make a log of what you see so
you can send it to someone (or print it out).

/dps

--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Good article on how to read coredump or use debugger

Hi,

Once you have the core open in VDB use "L" to create an abend.log from
the core. From the stack trace in the abend.log you can see what
process was running and so on.

There is little or no documentation on VDB or the NetWare Internal
Debugger, and there were a few articles in AppNotes many years ago which
offered a copy-book approach to stack walking - but that is generally
unnecessary since the abend.log does that for you in most cases. But
frankly these provide only the most superficial information. Sadly,
unless you've been coding NLM's for a while, most of the internals will
be just meaningless.

-- Bob

- - - - - - - - - - - - - - - - -
Robert Charles Mahar
Traffic Shaping Engine for NetWare
http://www.TrafficShaper.com
- - - - - - - - - - - - - - - - -

nsrdman@hotmail.com wrote:
> Hi Guys,
>
> Anyone know a good article to use debugger commands to indentify which
> process and threads causing abend and hopefully which function.
>
>
> Or does anyone has a sample steps ?
>
> I got a coredump file, I can open it, but have limited commands that I
> know.
>
>
> regards,
>
>
> nsrdman

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.