[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #1287: csc -deploy fails with modules
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #1287: csc -deploy fails with modules |
Date: |
Thu, 26 May 2016 21:02:07 -0000 |
#1287: csc -deploy fails with modules
----------------------+---------------------
Reporter: nxg | Owner:
Type: defect | Status: new
Priority: major | Milestone: someday
Component: unknown | Version: 4.10.x
Resolution: | Keywords:
----------------------+---------------------
Comment (by nxg):
Happy to, but ermmmm: could you advise me how best to do that? The
various breakpoint specifications I thought would work, in both `gdb` and
`lldb`, don't seem to have any effect (see below; I get the same odd lack
of effect in `lldb`), and I'm wondering if there's something subtle about
breakpoints in shared libraries that I haven't encountered before.
I'm sure I'm being dim here, and my google-fu seems weak today, but any
pointers would be appreciated.
{{{
[...]
(gdb) break runtime.c:panic
No symbol table is loaded. Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (runtime.c:panic) pending.
(gdb) run
Starting program: /private/tmp/chicken/main/main
warning:
`/BinaryCache/coreTLS/coreTLS-35.40.1~1/Objects/coretls.build/coretls.build
/Objects-normal/x86_64/system_coretls_vers.o': can't open to read symbols:
No such file or directory.
warning: Could not open OSO archive file
"/BinaryCache/coreTLS/coreTLS-35.40.1~1/Symbols/BuiltProducts/libcoretls_ciphersuites.a"
warning: Could not open OSO archive file
"/BinaryCache/coreTLS/coreTLS-35.40.1~1/Symbols/BuiltProducts/libcoretls_handshake.a"
warning: Could not open OSO archive file
"/BinaryCache/coreTLS/coreTLS-35.40.1~1/Symbols/BuiltProducts/libcoretls_record.a"
warning: Could not open OSO archive file
"/BinaryCache/coreTLS/coreTLS-35.40.1~1/Symbols/BuiltProducts/libcoretls_stream_parser.a"
[panic] nursery is too small - try higher setting using the `-:s' option -
execution terminated
[Inferior 1 (process 73628) exited with code 01]
(gdb) quit
}}}
--
Ticket URL: <http://bugs.call-cc.org/ticket/1287#comment:4>
CHICKEN Scheme <http://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
- [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/23
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/24
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/26
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/26
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules,
Chicken Trac <=
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27
- Re: [Chicken-janitors] #1287: csc -deploy fails with modules, Chicken Trac, 2016/05/27