From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: ia32 compatibility problem
Date: Tue, 31 Jul 2001 20:25:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005974@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005973@msgid-missing>
>>>>> On Tue, 31 Jul 2001 15:41:22 -0400, Bill Nottingham <notting@redhat.com> said:
Bill> Did abiword at least work with the warning?
No, it dies with a segfault. The backtrace is attached below. Note:
the symbol info is not complete, so some of the function names are
wrong. For example, I don't think the function that crashes is
iconv_close().
--david
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x403b0b43 in iconv_close () from /usr/i386-glibc22-linux/lib/libc.so.6
1: x/i $eip 0x403b0b43 <iconv_close+1935>: mov (%esi),%eax
(gdb) bt
#0 0x403b0b43 in iconv_close () from /usr/i386-glibc22-linux/lib/libc.so.6
#1 0x403b02b7 in iconv () from /usr/i386-glibc22-linux/lib/libc.so.6
#2 0x080fc028 in UT_Mbtowc::mbtowc ()
#3 0x080f8b0f in UT_UCS_strcpy_char ()
#4 0x080e4199 in ap_sb_Field_PageInfo::getDesiredWidth ()
#5 0x080e3e5c in AP_StatusBar::setView ()
#6 0x080d04e3 in AP_UnixFrame::_showDocument ()
#7 0x080d0dd7 in AP_UnixFrame::loadDocument ()
#8 0x080d1b7c in AP_UnixFrame::loadDocument ()
#9 0x080cf859 in AP_UnixApp::parseCommandLine ()
#10 0x080cf2d4 in AP_UnixApp::main ()
#11 0x080ce01c in main ()
#12 0x403afd4c in __libc_start_main ()
from /usr/i386-glibc22-linux/lib/libc.so.6
prev parent reply other threads:[~2001-07-31 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 19:41 [Linux-ia64] Re: ia32 compatibility problem Bill Nottingham
2001-07-31 20:25 ` David Mosberger [this message]
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=marc-linux-ia64-105590693005974@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.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