l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2008 Mar 03 10:34

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox] LUGOD advertisement...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox] LUGOD advertisement...

On Fri, 22 Jun 2001, Micah Cowan wrote:

> But that's *exactly* the point!  BSODs and coredumps are at completely
> different levels!  UNIX coredumps are analagous to Windows blandly
> announcing that your application has quit due to some unknown error
> (except with coredumps you have a better chance of determining what
> that error was); BSODs are analogous to full-on-kernel panics (uh,

NT has the equivalent of a coredump. On a BSOD crash, it can dump the
contents of physical memory to a file, and the amount of what it drops is
controllable by the administrator.  This file is useful for debugging what

I've never seen applications dump core in Windows, but presumably that's
because the debugging in Windows is done differently... (via the debug
API) ... It wouldn't be too tough to add a core-dump style feature (if it
doesn't already exist somewhere as some kind of option I'm unaware of.)
If you catch the exception with a debugger attached to the process, you might
not necessarily need such a thing as a coredump.  You can use
ReadProcessMemory() and GetThreadContext() API's to retrieve relevant
information, and then use that.  Somehow, when applications crash
sometimes in Windows, I get a box asking if I want to debug the
application.  Methinks this prompt is brought up because somewhere in the
registry it knows that there is a debugger registered somewhere in the
system (but I am not sure.)  In Visual C++, when you catch an
application for debugging, it is able to give you call stack information
too.  I think this can happen if it has the debugging symbols within the
same directory as the executable... Otherwise, it's just a disassembly of
the process and register contents, iirc.

Pavan xxxxxx (xxxxxx@uiuc.edu)   http://www.students.uiuc.edu/~xxxxxx
Computer Engineering Student     University of Illinois @ Urbana-Champaign

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.