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

Groups > comp.lang.c++ > #2937

Re: program that ain't crash inside debugger

Show all headers | View raw

In article <73ae9c50-8e26-4d71-9ca0-f825a6ea411e@a19g2000prj.googlegroups.com>
	console kid <sandundhammikaperera@gmail.com> writes:
>any idea how could I pinpoint the error?

I seem to recall that some environments support ways to force any
crash to leave a core dump file.  If you can do that, then you can
debug the post-crash state of the program.

Otherwise, the details of the crash could point somewhere.  How do
you know it crashes?  Are there any details (addresses, etc.) in
the message?

Still, all of this also would be more meaningful in a group specific
to your toolset and/or OS.

-- 
Drew Lawson            |  It's not enough to be alive
                       |  when your future's been deferred

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

program that ain't crash inside debugger console kid <sandundhammikaperera@gmail.com> - 2011-03-31 05:20 -0700
  Re: program that ain't crash inside debugger Puppet_Sock <puppet_sock@hotmail.com> - 2011-03-31 07:10 -0700
  Re: program that ain't crash inside debugger "Default User" <defaultuserbr@yahoo.com> - 2011-03-31 12:26 -0500
  Re: program that ain't crash inside debugger console kid <sandundhammikaperera@gmail.com> - 2011-03-31 10:51 -0700
    Re: program that ain't crash inside debugger Victor Bazarov <v.bazarov@comcast.invalid> - 2011-03-31 14:04 -0400
    Re: program that ain't crash inside debugger drew@furrfu.invalid (Drew Lawson) - 2011-03-31 18:10 +0000
    Re: program that ain't crash inside debugger "Balog Pal" <pasa@lib.hu> - 2011-03-31 20:21 +0200

csiph-web