tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Tinycc failing to compile fossil-scm on ubuntu 13.10


From: Domingo Alvarez Duarte
Subject: Re: [Tinycc-devel] Tinycc failing to compile fossil-scm on ubuntu 13.10 arm
Date: Sun, 30 Mar 2014 16:21:43 +0100

After writing the previous post I decided to also check with fossil compiled with gcc and it gives the same result so this particular issue is not something from tinycc.

-----
address@hidden:~/dev/fossil$ gdb --args ./fossil-gcc server
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/mingo/dev/fossil/fossil-gcc...done.
(gdb) b page_timeline
Breakpoint 1 at 0x53adc: file ./src/timeline.c, line 1063.
(gdb) set follow-fork-mode child
(gdb) r
Starting program: /home/mingo/dev/fossil/./fossil-gcc server

Program received signal SIGILL, Illegal instruction.
0xb6ec53c8 in ?? () from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
(gdb) bt
#0  0xb6ec53c8 in ?? () from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
Cannot access memory at address 0x0
#1  0xb6ec3090 in OPENSSL_cpuid_setup ()
   from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
#2  0xb6feb028 in call_init (env=0xbefff790, argv=0xbefff784, argc=2, 
    l=<optimized out>) at dl-init.c:84
#3  call_init (l=<optimized out>, argc=2, argv=0xbefff784, env=0xbefff790)
    at dl-init.c:34
#4  0xb6feb0a8 in _dl_init (main_map=0xb6fff958, argc=2, argv=0xbefff784, 
    env=0xbefff790) at dl-init.c:133
#5  0xb6fe0c62 in _dl_start_user () from /lib/ld-linux-armhf.so.3
#6  0xb6fe0c62 in _dl_start_user () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


On Sun, Mar 30, 2014 at 4:17 PM, Domingo Alvarez Duarte <address@hidden> wrote:
Hello all !

Trying to find why fossil-scm compiled with tinycc do not work properly on ubuntu 13.10 arm inside a nexus5 and trying to use the debugger I've got the messages shown bellow, on my ubuntu 12.04 X86_64 gdb works fine with fossil-scm compiled by tinycc, it's here just in case someone can have a clue of what's the problem.

-----
address@hidden:~/dev/fossil$ gdb --args ./fossil server
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
For bug reporting instructions, please see:
Reading symbols from /home/mingo/dev/fossil/fossil...done.
(gdb) set follow-fork-mode child
(gdb) b page_timeline
Breakpoint 1 at 0xade6c: file bld/timeline_.c, line 1059.
(gdb) r
Starting program: /home/mingo/dev/fossil/./fossil server

Program received signal SIGILL, Illegal instruction.
0xb6ec53c8 in ?? () from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
(gdb) bt
#0  0xb6ec53c8 in ?? () from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
Cannot access memory at address 0x0
#1  0xb6ec3090 in OPENSSL_cpuid_setup ()
   from /lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
#2  0xb6feb028 in call_init (env=0xbefff790, argv=0xbefff784, argc=2, 
    l=<optimized out>) at dl-init.c:84
#3  call_init (l=<optimized out>, argc=2, argv=0xbefff784, env=0xbefff790)
    at dl-init.c:34
#4  0xb6feb0a8 in _dl_init (main_map=0xb6fff958, argc=2, argv=0xbefff784, 
    env=0xbefff790) at dl-init.c:133
#5  0xb6fe0c62 in _dl_start_user () from /lib/ld-linux-armhf.so.3
#6  0xb6fe0c62 in _dl_start_user () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]