On Wed, Nov 27, 2019 at 09:16:51AM -0500, David Higgs wrote:
> I don't speak ktrace but looks like alignment problems with a stack
> variable. What does gdb report?
>
> --david
Hi David,
I'm going to upgrade to -current and then report back.. it'll take me a few
days to do that (I'm super slow).
FWIW though:
----->
(gdb) run configtest
Starting program: /usr/local/bin/dddctl configtest
(no debugging symbols found)
ptrace: Invalid argument.
_thread_sys_fork () at -:15
15 -: No such file or directory.
in -
(gdb) bt
#0 _thread_sys_fork () at -:15
#1 0x0000004236424ac8 in _libc_fork_wrap ()
at /usr/src/lib/libc/sys/w_fork.c:51
#2 0x0000003d5b7b3028 in drop_privs () from /usr/local/bin/dddctl
#3 0x000000ffffffce60 in ?? ()
warning: GDB can't find the start of the function at 0xffffffce60.
GDB is unable to find the start of the function at 0xffffffce60
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0xffffffce60 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
Previous frame inner to this frame (corrupt stack?)
<----
I'll see if this sort of issue repeats after I upgrade the octeon router
to -current.
Thanks!
-peter
No comments:
Post a Comment