public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Kuntze <nicolai@hubrich.org>
To: Stas Sergeev <stsp@aknet.ru>
Cc: linux-msdos@vger.kernel.org
Subject: Re: S-Lang Error
Date: Sat, 14 Feb 2004 09:47:55 +0100 (CET)	[thread overview]
Message-ID: <4900571.1076748475162.SLOX.WebMail.wwwrun@linux.hubrich.org> (raw)
In-Reply-To: 402D3FFF.7050502@aknet.ru

Am Fr 13.02.2004 22:22, Stas Sergeev <stsp@aknet.ru> schrieb:

> 
> Hello.
> 
> Nicolai Kuntze wrote:
> > I've browsed the source, but after this I'm not further then before. I 
> > have a leavedos(1|0x1) and I think I get this every time the execution 
> > of the program in the box failes. Can I switch on some debugging to get 
> > a closer look on this?
> The best way to investigate the
> source of leavedos() call would be
> to compile dosemu with debug info,
> start it under gdb and, setting the
> break-point to leavedos(), produce a
> stack trace when that break-point is
> reached.
> -

I am unexperienced in such things and so I have never used gdb before. So, here some, possibly stupid, questions:
Is it possible to automate this. The error occurs from time to time, but without any resonably pattern. This in mind, I need a way to always start the debugger but only to record the crash.

Thanks for your help.

Nicolai


---- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.



  reply	other threads:[~2004-02-14  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 21:22 S-Lang Error Stas Sergeev
2004-02-14  8:47 ` Nicolai Kuntze [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-12 19:49 Nicolai Kuntze
2004-02-12 21:31 ` Bart Oldeman
2004-02-13 14:13   ` Nicolai Kuntze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4900571.1076748475162.SLOX.WebMail.wwwrun@linux.hubrich.org \
    --to=nicolai@hubrich.org \
    --cc=linux-msdos@vger.kernel.org \
    --cc=stsp@aknet.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox