From: Sean Hunter <sean@dev.sportingbet.com>
To: Tony Hoyle <tmh@nothing-on.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: just-in-time debugging?
Date: Tue, 1 May 2001 08:25:36 +0100 [thread overview]
Message-ID: <20010501082536.A30970@dev.sportingbet.com> (raw)
In-Reply-To: <20010428201708.E629E13F6A@mail.cvsnt.org>
In-Reply-To: <20010428201708.E629E13F6A@mail.cvsnt.org>; from tmh@nothing-on.tv on Sat, Apr 28, 2001 at 09:17:10PM +0100
My approach is something like the others. I developed a small wrapper to catch
unaligned traps on alpha. What it does is run a program in gdb with some
specified arguments (it also sets up so that the process gets a SIGBUS when it
does an unaligned access, but that's probably not relevant here).
Any case, its available by anonymous ftp at ftp://uncarved.com/unaligned.c
in case you're interested...
Sean
On Sat, Apr 28, 2001 at 09:17:10PM +0100, Tony Hoyle wrote:
> Is there a way (kernel or userspace... doesn't matter) that gdb/ddd
> could be invoked when a program is about
> to dump core, or perhaps on a certain signal (that the app could deliver
> to itself when required). The latter case
> is what I need right now, as I have to debug an app that breaks
> seemingly randomly & I need to halt when
> certain assertions fail. Core dumps aren't much use as you can't resume
> them, otherwise I'd just force a segfault
> or something.
>
> I had a look at the do_coredump stuff and it looks like it could be
> altered to call gdb in the same way that
> modprobe gets called by kmod... however I don't sufficiently know the
> code to work out whether it'd work properly
> or not.
>
> A patch to glibc would perhaps be better, but I know that code even
> less!
>
> Something like responding to SIGTRAP would probably be ideal.
>
> Tony
>
> --
>
> "Two weeks before due date, the programmers work 22 hour days cobbling an
> application from... (apparently) one programmer bashing his face into the
> keyboard." -- Dilbert
>
> tmh@magenta-netlogic.com http://www.nothing-on.tv
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-05-01 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 20:17 just-in-time debugging? Tony Hoyle
2001-04-28 20:44 ` Davide Libenzi
2001-04-28 21:00 ` Tony Hoyle
2001-04-28 21:06 ` Davide Libenzi
2001-05-01 7:25 ` Sean Hunter [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 20:42 Dan Kegel
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=20010501082536.A30970@dev.sportingbet.com \
--to=sean@dev.sportingbet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmh@nothing-on.tv \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.