On Sat, Feb 20, 2016 at 4:42 AM, Andy Bradford <[email protected]> wrote:
> Thus said Martin Gagnon on Fri, 19 Feb 2016 20:56:47 -0500: > > > This is not usually stack addresses? > > Yes, for allocated memory, but how big is the stack that supports an > address that big? > Dunno. Just kinda randomly taking a backtrace from a random program... #0 0x00007ffff76b6810 in __read_nocancel () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007ffff79b9a7d in rl_getc () from /lib/x86_64-linux-gnu/libreadline.so.6 #2 0x00007ffff79ba2ae in rl_read_key () from /lib/x86_64-linux-gnu/libreadline.so.6 #3 0x00007ffff79a3edc in readline_internal_char () from /lib/x86_64-linux-gnu/libreadline.so.6 #4 0x00007ffff79a4625 in readline () from /lib/x86_64-linux-gnu/libreadline.so.6 #5 0x000000000040c4a8 in s2sh_line_read (prompt=0x48051d "s2> ") at shell.c:636 #6 0x000000000040cc8d in s2sh_interactive (se=0x7fffffffcfb0) at shell.c:842 #7 0x000000000040d217 in s2sh_main2 (se=0x7fffffffcfb0) at shell.c:1021 #8 0x000000000040d933 in s2sh_main (argc=1, argv=0x7fffffffdb78) at shell.c:1157 #9 0x000000000040eaaf in main (argc=1, argv=0x7fffffffdb78) at shell.c:1555 i see lots of 0x7ffffff....s in there, and i happen to know that se=... is indeed a stack-allocated object. i'm a bit surprised that argv is, but not overly so. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
