Pike-devel February 2015

pike-devel@lists.lysator.liu.se

4 participants
15 discussions

Start a nNew thread

Re: gdb_backtraces()
by Mirar ＠ Pike developers forum 10 Feb '15

10 Feb '15

I probably need some sort of URL too?

1 0

gdb_backtraces()
by Mirar ＠ Pike developers forum 10 Feb '15

10 Feb '15

Should gdb_backtraces() still work in 8.0? (gdb) call gdb_backtraces() Program received signal SIGSEGV, Segmentation fault. 0x0005e0c4 in gdb_backtrace (thread_id=<optimized out>) at /home/pi/Pike-v8.0.10/src/interpret.c:3345 3345 args = DO_NOT_WARN((INT32) MINIMUM(f->num_args, Pike_sp - f->locals)); The program being debugged was signaled while in a function called from GDB. GDB remains in the frame where the signal was received. To change this behavior use "set unwindonsignal on". Evaluation of the expression containing the function (gdb_backtraces) will be abandoned. When the function is done executing, GDB will silently stop. (gdb) p *f $2 = {refs = 1, args = 1, fun = 9, num_locals = 1, num_args = 1, flags = 0, ident = 0, next = 0x1f7bd84, scope = 0x0, pc = 0x0, return_addr = 0x200336f "\024\217-", locals = 0xb6ac5098, save_sp = 0xb6ac5090, expendible = 0xb6ac5098, save_mark_sp = 0xb6a63000, mark_sp_base = 0xb6a63000, current_object = 0x1f78608, current_program = 0x1f726ec, context = 0x1f858dc, current_storage = 0x1f8ef50 "`\357\370\001\003"} (gdb) p *Pike_interpreter_pointer Cannot access memory at address 0x0 (gdb) info threads Id Target Id Frame * 2 Thread 0xb65c4470 (LWP 19748) "pike" 0xb6e9e250 in nanosleep () from /lib/arm-linux-gnueabihf/libpthread.so.0 1 Thread 0xb6fde000 (LWP 19742) "pike" 0x0005e0c4 in gdb_backtrace (thread_id=<optimized out>) at /home/pi/Pike-v8.0.10/src/interpret.c:3345 Both threads look like normal pike interpreter threads, except the one with the crashed gdb_backtraces() on top. This is repeatable, but not from just running Hilfe. ARM (Pi).

3 3

Re: Build failure when HAVE_NETTLE_ECDSA_H not set
by Chris Angelico 07 Feb '15

07 Feb '15

On Sat, Feb 7, 2015 at 10:30 PM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > These symbols are only useful when ECC is available, so they should be > guarded in the same way as their definitions. > > Fixed. > > Thanks for the report. Thanks, working nicely! ChrisA

1 0

Build failure when HAVE_NETTLE_ECDSA_H not set
by Chris Angelico 07 Feb '15

07 Feb '15

/home/rosuav/pike/src/post_modules/Nettle/hogweed.cmod:1008:1: error: ‘SECP192R1’ undeclared (first use in this function) The symbols are defined inside a block guarded by HAVE_NETTLE_ECDSA_H, but then are used in hogweed_init, which is unguarded. One possible fix would be to move the defines outside the HAVE_ block; branch rosuav/survive_no_nettle_ecdsa does this. Is this the right approach, or is there a better way? ChrisA

2 1

Small tweak to Process.run() new feature
by Chris Angelico 06 Feb '15

06 Feb '15

In Pike 8.1, Process.run() will accept functions for stdout and stderr, as was discussed here a while ago. I just tweaked that to check for *callables* rather than specifically functions, which allows easy tee'ing of the output: Process.run( ({"some_command","with","args"}), (["stdout":({write,Stdio.File("output.txt","wct")->write}) ]) ); Maybe my idea of coolness is disrupted by the 36 degree weather we're having here at the moment, but I just love the idea of putting multiple outputs simply as multiple functions! ChrisA

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel February 2015