Error building qnx cross-gdb 6.3

Error building qnx cross-gdb 6.3

[Ion Gaztañaga]

Hello to all,

 When trying to build a cross-gdb (gdb 6.3) host=cygwin 
target=i386-pc-nto-qnx6.3.0 I've got some problems. I have gcc 3.4.3 and 
binutils 2.15 cross-compiled in /tools/i386-pc-nto-qnx6.3.0 working fine and 
/tools/i386-pc-nto-qnx6.3.0/bin has i386-pc-nto-qnx6.3.0-* executables and 
this directory is in my PATH in the last position.

I unzip gdb-6.3 sources in /src, I make a objdir directory 
(/src/gdb-6.3/objdir), I cd to it and I type:

$ 
../configure --target=i386-pc-nto-qnx6.3.0 --prefix=/tools/i386-pc-nto-qnx6.3.0

All fine

$ make

After some compilations, I get:

$ No rule to make target `remote-nto.o', needed by `libgdb.a'

and remote-nto is not in the gdb source tree. If I remove remote-nto.o from 
objdir/gdb Makefile in the following lines:

TDEPFILES = i386-tdep.o i387-tdep.o corelow.o solib.o solib-svr4.o \
            i386-nto-tdep.o nto-tdep.o remote-nto.o

I get:

ar: creating libgdb.a
ranlib libgdb.a
make[1]: *** No rule to make target `../intl/libintl.a', needed by 
`gdb.exe'.  Stop.

If I change these other lines in objdir/gdb/Makefile

INTL_DIR = ../intl
INTL = $(top_builddir)/../intl/libintl.a
INTL_DEPS = $(top_builddir)/../intl/libintl.a
INTL_SRC = $(srcdir)/$(INTL_DIR)
INTL_CFLAGS = -I$(INTL_DIR) -I$(INTL_SRC)

with

INTL_DIR = /lib
INTL = /lib/libintl.a
INTL_DEPS = /lib/libintl.a
INTL_SRC = $(srcdir)/$(INTL_DIR)
INTL_CFLAGS = -I$(INTL_DIR) -I$(INTL_SRC)

pointing to the cygwin intl library, the compilation ends successfully with:

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)
make[2]: Entering directory `/src/gdb-6.3/objdir/gdb'
make[3]: Entering directory `/src/gdb-6.3/objdir/gdb/doc'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/src/gdb-6.3/objdir/gdb/doc'
make[2]: Leaving directory `/src/gdb-6.3/objdir/gdb'
make[1]: Leaving directory `/src/gdb-6.3/objdir/gdb'

but i386-pc-nto-qnx6.3.0-gdb gives a core when executed, so I don't know if 
libintl.a should be the native cygwin lib or other lib I am missing.

I have no experience building cross-gdb so maybe I'm missing something. But 
the first error regarding remote-nto.o is very confusing to me (seems like a 
missing c file), and I don't know which switch I have to use to solve this 
libintl stuff. I've seen that there is a intl directory in gdb-5.0 release 
but it is not present in gdb-6.3, do I have to get it somewhere?.

Thanks and regards,

Ion

Re: Error building qnx cross-gdb 6.3

[Daniel Jacobowitz]

On Mon, May 23, 2005 at 05:50:19PM +0200, Ion Gaztañaga wrote:
> Hello to all,
> 
> When trying to build a cross-gdb (gdb 6.3) host=cygwin 
> target=i386-pc-nto-qnx6.3.0 I've got some problems. I have gcc 3.4.3 and 
> binutils 2.15 cross-compiled in /tools/i386-pc-nto-qnx6.3.0 working fine 
> and /tools/i386-pc-nto-qnx6.3.0/bin has i386-pc-nto-qnx6.3.0-* executables 
> and this directory is in my PATH in the last position.
> 
> I unzip gdb-6.3 sources in /src, I make a objdir directory 
> (/src/gdb-6.3/objdir), I cd to it and I type:
> 
> $ 
> ../configure --target=i386-pc-nto-qnx6.3.0 
> --prefix=/tools/i386-pc-nto-qnx6.3.0
> 
> All fine
> 
> $ make
> 
> After some compilations, I get:
> 
> $ No rule to make target `remote-nto.o', needed by `libgdb.a'
> 
> and remote-nto is not in the gdb source tree. If I remove remote-nto.o from 
> objdir/gdb Makefile in the following lines:

Kris?  This could never have worked.

> ar: creating libgdb.a
> ranlib libgdb.a
> make[1]: *** No rule to make target `../intl/libintl.a', needed by 
> `gdb.exe'.  Stop.

I don't know what causes this but try --disable-nls.  Does that help?

> I have no experience building cross-gdb so maybe I'm missing something. But 
> the first error regarding remote-nto.o is very confusing to me (seems like 
> a missing c file), and I don't know which switch I have to use to solve 
> this libintl stuff. I've seen that there is a intl directory in gdb-5.0 
> release but it is not present in gdb-6.3, do I have to get it somewhere?.

It was recently removed.  I don't remember the outcome of that
discussion.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: Error building qnx cross-gdb 6.3

[Ion Gaztañaga]

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

RE: Error building qnx cross-gdb 6.3

[Dave Korn]

----Original Message----
>From: Ion Gaztañaga
>Sent: 24 May 2005 05:58


> 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.ex
e,
> 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


  Why don't you debug it with native gdb?  You could also get a more
meaningful backtrace by running

addr2line --exe=/tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb.exe

and cutting and pasting the column of addresses under 'Function' into it.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Re: Error building qnx cross-gdb 6.3

[Kris Warkentin]

You're going into somewhat uncharted territories here.  We _DO_ cross 
compile gdb targetting qnx but the GNU cvs doesn't have all the files 
yet for remote debugging.  It only has self-hosted, i386 targetting.

If you would like a drop of the full port of the sources, go to 
http://www.qnx.com/download/group.html?programid=11358 and you can find 
compiled binaries and source for gdb-6.2.1.  You may need to create a 
free myQNX account.

I also have 6.3.0 sources if you would like them.  For what it's worth, 
I build gdb under cygwin with 'configure --disable-sim --disable-nls 
--disable-gdbtk --target=i386-nto'

cheers,

Kris

Ion Gaztañaga wrote:

>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-gd
>b.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
>  
>

Re: Error building qnx cross-gdb 6.3

[Ion Gaztañaga]

Hello to all,

  Thanks Kris for the link. I thought cross-compilation was already in head 
with remote debugging. Anyway if it is useful I've debugged a bit.
It may seem a joke but the only commands I knew about gdb were r, c, and bt 
(yes, building a tool I never use is not usual but work is like that...) But 
anyway, this seems enough to get some hints:

$ 
addr2line.exe --exe=/tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb.exe
0042012D
/src/gdb-6.3/objdir/gdb/../../gdb/infrun.c:3077
004E0F60
/src/gdb-6.3/objdir/gdb/../../gdb/nto-tdep.c:322
00425F89
/src/gdb-6.3/objdir/gdb/init.c:123
00403DB6
/src/gdb-6.3/objdir/gdb/../../gdb/top.c:1766
00401616
/src/gdb-6.3/objdir/gdb/../../gdb/main.c:527
00402281
/src/gdb-6.3/objdir/gdb/../../gdb/top.c:525
004020F5
/src/gdb-6.3/objdir/gdb/../../gdb/top.c:431
004022E0
/src/gdb-6.3/objdir/gdb/../../gdb/top.c:538
00401DF3
/src/gdb-6.3/objdir/gdb/../../gdb/main.c:814
004010AA
/src/gdb-6.3/objdir/gdb/../../gdb/gdb.c:36
61005F34
??:0
6100614B
??:0

------------------------------------------------

igaztanaga@ion ~
$ gdb /tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb.exe
GNU gdb 2003-09-20-cvs (cygwin-special)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) c
The program is not being run.
(gdb) r
Starting program: 
/tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb.exe

Program received signal SIGSEGV, Segmentation fault.
0x0042012d in signal_stop_update (signo=57, state=0)
    at ../../gdb/infrun.c:3077
3077      int ret = signal_stop[signo];
(gdb) bt
#0  0x0042012d in signal_stop_update (signo=57, state=0)
    at ../../gdb/infrun.c:3077
#1  0x004e0f60 in _initialize_nto_tdep () at ../../gdb/nto-tdep.c:321
#2  0x00425f89 in initialize_all_files () at init.c:122
#3  0x00403db6 in gdb_init (
    argv0=0x10101f70 
"/tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb")
 at ../../gdb/top.c:1765
#4  0x00401616 in captured_main (data=0x22f000) at ../../gdb/main.c:520
#5  0x00402281 in do_catch_errors (uiout=0x5834d0, data=0x22efc0)
    at ../../gdb/top.c:524
#6  0x004020f5 in catcher (func=0x402270 <do_catch_errors>,
    func_uiout=0x5834d0, func_args=0x22efc0, func_val=0x22efb8,
    func_caught=0x22efbc, errstring=0x58e0e2 "", gdberrmsg=0x0, mask=6)
    at ../../gdb/top.c:431
#7  0x004022e0 in catch_errors (func=0x401110 <captured_main>,
    func_args=0x22f000, errstring=0x58e0e2 "", mask=6) at 
../../gdb/top.c:536
#8  0x00401df3 in gdb_main (args=0x22f000) at ../../gdb/main.c:810
#9  0x004010aa in main (argc=1, argv=0x10101f40) at ../../gdb/gdb.c:35


It seems that in the signal_stop function array is not initialized. 
_initialize_infrun is not called?

(gdb) print signal_stop
$1 = (unsigned char *) 0x0

After some breakpoints (yes, I've learnt that right now ;-) ) I find that:

_initialize_nto_tdep is called before _initialize_infrun so signal arrays 
are not initialized. I can confirm this in gdb\init.c file of my build-dir

I will return when gdb 6.4 is out ;-) . Regards and thanks.

Ion


----- Original Message ----- 
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Ion Gaztañaga" <ion_g_m@terra.es>
Cc: "Daniel Jacobowitz" <drow@false.org>; <gdb@sources.redhat.com>
Sent: Tuesday, May 24, 2005 5:54 PM
Subject: Re: Error building qnx cross-gdb 6.3


> You're going into somewhat uncharted territories here.  We _DO_ cross 
> compile gdb targetting qnx but the GNU cvs doesn't have all the files yet 
> for remote debugging.  It only has self-hosted, i386 targetting.
>
> If you would like a drop of the full port of the sources, go to 
> http://www.qnx.com/download/group.html?programid=11358 and you can find 
> compiled binaries and source for gdb-6.2.1.  You may need to create a free 
> myQNX account.
>
> I also have 6.3.0 sources if you would like them.  For what it's worth, I 
> build gdb under cygwin with 
> 'configure --disable-sim --disable-nls --disable-gdbtk --target=i386-nto'
>
> cheers,
>
> Kris

Re: Error building qnx cross-gdb 6.3

[Kris Warkentin]

Ion Gaztañaga wrote:

>After some breakpoints (yes, I've learnt that right now ;-) ) I find
>that:
>
>_initialize_nto_tdep is called before _initialize_infrun so signal
>arrays 
>are not initialized. I can confirm this in gdb\init.c file of my
>build-dir
>  
>

Ah..this looks familiar.  I'm maintaining 4 or 5 different gdb branches 
and it's possible that some of my signal handling code didn't make it 
back into the head.  Thanks for finding this.  I'll look into it.

cheers,

Kris

Re: Error building qnx cross-gdb 6.3

[Kris Warkentin]

Daniel Jacobowitz wrote:

>On Mon, May 23, 2005 at 05:50:19PM +0200, Ion Gaztañaga wrote:
>  
>
>>Hello to all,
>>
>>When trying to build a cross-gdb (gdb 6.3) host=cygwin 
>>target=i386-pc-nto-qnx6.3.0 I've got some problems. I have gcc 3.4.3
>>    
>>
>and 
>  
>
>>binutils 2.15 cross-compiled in /tools/i386-pc-nto-qnx6.3.0 working
>>    
>>
>fine 
>  
>
>>and /tools/i386-pc-nto-qnx6.3.0/bin has i386-pc-nto-qnx6.3.0-*
>>    
>>
>executables 
>  
>
>>and this directory is in my PATH in the last position.
>>
>>I unzip gdb-6.3 sources in /src, I make a objdir directory 
>>(/src/gdb-6.3/objdir), I cd to it and I type:
>>
>>$ 
>>../configure --target=i386-pc-nto-qnx6.3.0 
>>--prefix=/tools/i386-pc-nto-qnx6.3.0
>>
>>All fine
>>
>>$ make
>>
>>After some compilations, I get:
>>
>>$ No rule to make target `remote-nto.o', needed by `libgdb.a'
>>
>>and remote-nto is not in the gdb source tree. If I remove remote-nto.o
>>    
>>
>from 
>  
>
>>objdir/gdb Makefile in the following lines:
>>    
>>
>
>Kris?  This could never have worked.
>

Argh...my bad.  That works on my box (because I have the remote files in 
my sandbox) but not on anyone elses.  The file gdb/config/i386/nto.mt 
accidentally got checked in with "remote-nto.o" in it even though I 
haven't checked remote-nto.c into your cvs.  If you remove that line, it 
should be fine.

I'll fix that right away.

cheers,

Kris