From: "Ion Gaztañaga" <ion_g_m@terra.es>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sources.redhat.com>, <kewarken@qnx.com>
Subject: Re: Error building qnx cross-gdb 6.3
Date: Tue, 24 May 2005 04:55:00 -0000 [thread overview]
Message-ID: <000b01c5601d$2ff04240$0a001aac@amd1ghzwinxp> (raw)
In-Reply-To: <20050523155353.GA3642@nevyn.them.org>
Hello again,
I've retried to cross-compile gdb with cygwin host and i386-pc-nto-qnx6.3.0
target. This time with --disable-nls. The remote-nto error was there of
course, but after removing that from Makefile, all compilation was successul
with these warnings:
Info: resolving _LINES by linking to __imp__LINES (auto-import)
Info: resolving _COLS by linking to __imp__COLS (auto-import)
Info: resolving _stdscr by linking to __imp__stdscr (auto-import)
Info: resolving _curscr by linking to __imp__curscr (auto-import)
Info: resolving _LINES by linking to __imp__LINES (auto-import)
Info: resolving _COLS by linking to __imp__COLS (auto-import)
Info: resolving _stdscr by linking to __imp__stdscr (auto-import)
Info: resolving _curscr by linking to __imp__curscr (auto-import)
Anyway the created and installed i386-pc-nto-qnx6.3.0-gdb.exe file (6.563KB)
does not work:
igaztanaga@ion /tools/i386-pc-nto-qnx6.3.0/bin
$ ./i386-pc-nto-qnx6.3.0-gdb.exe
Segmentation fault (core dumped)
The created i386-pc-nto-qnx6.3.0-gdb.exe.stackdump was:
Exception: STATUS_ACCESS_VIOLATION at eip=0042012D
eax=00000039 ebx=00000039 ecx=00000000 edx=00000039 esi=61782CD8
edi=00000001
ebp=0022ECE8 esp=0022ECE4
program=C:\cygwin\tools\i386-pc-nto-qnx6.3.0\bin\i386-pc-nto-qnx6.3.0-gdb.exe,
pid 920, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022ECE8 0042012D (00000039, 00000000, 0062A650, 005E122C)
0022ED28 004E0F60 (61782CD8, 00000000, 0022ED48, 00403DB6)
0022ED38 00425F89 (006283B0, 00000400, 0022EE98, 00401616)
0022ED48 00403DB6 (61782D00, 61782CD8, 0058E0E2, 00583000)
0022EE98 00401616 (0022F050, 0022F060, 0022EFD8, 004020F5)
0022EEA8 00402281 (005834D0, 0022F010, 0022EFB4, 00000000)
0022EFD8 004020F5 (00402270, 005834D0, 0022F010, 0022F008)
0022F018 004022E0 (00401110, 0022F050, 0058E0E2, 00000006)
0022F038 00401DF3 (0022F050, 00000754, 0022F068, 6109106A)
0022F068 004010AA (00000001, 61782CD8, 101000A8, 0022F0C0)
0022F0A8 61005F34 (0022F0C0, 7C920833, 77D197E4, 77D19812)
0022FF88 6100614B (00000000, 00000000, 00000000, 00000000)
End of stack trace
Thanks and regards,
Ion
next prev parent reply other threads:[~2005-05-24 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 15:47 Ion Gaztañaga
2005-05-23 15:53 ` Daniel Jacobowitz
2005-05-24 4:55 ` Ion Gaztañaga [this message]
2005-05-24 14:09 ` Dave Korn
2005-05-24 15:53 ` Kris Warkentin
2005-05-24 17:19 ` Ion Gaztañaga
2005-05-24 18:55 ` Kris Warkentin
2005-05-24 15:37 ` Kris Warkentin
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='000b01c5601d$2ff04240$0a001aac@amd1ghzwinxp' \
--to=ion_g_m@terra.es \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.com \
/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