From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: Guillaume Laures <guillaume.laures@noos.fr>
Cc: linuxppc <linuxppc-dev@lists.linuxppc.org>
Subject: Re: XFree86-4.0.99.2
Date: Mon, 09 Apr 2001 10:11:28 +0200 [thread overview]
Message-ID: <3AD16EB0.738E278E@iiic.ethz.ch> (raw)
In-Reply-To: 986767730.17213.0.camel@pmg4.gom.net
Guillaume Laures wrote:
> #0 0xfe0bea8 in kill () at soinit.c:64
> #1 0xfe0bd24 in raise () at ../sysdeps/posix/raise.c:27
> #2 0xfe0d3d4 in abort () at ../sysdeps/generic/abort.c:139
> #3 0x10025bbc in ddxGiveUp ()
> #4 0x10025cb0 in AbortDDX ()
> #5 0x100a9ae0 in GiveUp ()
> #6 0x100ab5d8 in FatalError ()
> #7 0x1003c6ec in xf86SigHandler ()
> #8 <signal handler called>
> #9 0x1030aa04 in ?? ()
> #10 0x0 in ?? ()
[...]
> I tried looking for soinit.c in the i128 files but this didn't give any
> result, and I cannot find it trhough the whole source; any idea on where
> to head on ???
I suppose #0-#2 are from glibc and not interesting.
The interesting parts are #9 and #10, which are probably in loadable modules
so gdb can't handle them correctly. You could build a static server (#define
DoLoadableServer NO in xc/config/cf/host.def) and try with that.
PS: Has anyone tried porting the module aware gdb?
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-09 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15056.36750.453557.759357@ipa.ne.mediaone.net>
[not found] ` <3AD0AABE.1020605@vacuumgenesis.com>
[not found] ` <15056.55761.845494.317224@ipa.ne.mediaone.net>
2001-04-08 22:08 ` XFree86-4.0.99.2 Guillaume Laures
2001-04-08 22:39 ` XFree86-4.0.99.2 Kaoru Fukui
2001-04-09 8:11 ` Michel Dänzer [this message]
2001-04-09 16:32 ` XFree86-4.0.99.2 Michael Schmitz
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=3AD16EB0.738E278E@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=guillaume.laures@noos.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).