Displaying 4 results from an estimated 4 matches for "debug_segv".
Did you mean:
debug_env
2014 Oct 01
0
Useful tip: Run guestfsd under gdb and print stack trace on exit
...t
upstreamable right now.
Example usage:
$ ./run guestfish -v -x -a /dev/null run : debug segv ""
[...]
libguestfs: trace: launch = 0
libguestfs: trace: debug "segv" ""
guestfsd: main_loop: new request, len 0x34
Program received signal SIGSEGV, Segmentation fault.
debug_segv (subcmd=0x4687050 "segv", argc=0, argv=0x4687070) at debug.c:223
223\tdebug.c: No such file or directory.
#0 debug_segv (subcmd=0x4687050 "segv", argc=0, argv=0x4687070) at debug.c:223
#1 0x000000000042e083 in debug_stub (xdr_in=<optimized out>) at stubs.c:2557
#2 0x000...
2010 Aug 26
4
[REPOST] guestfsd core capture, and virt-rescue clean shutdown
This is a repost of a previously posted set. It's been updated following review
comments.
[PATCH 1/4] Add a core_pattern debug command
Added missing return statements.
[PATCH 2/4] Call sync after guestfsd exits
Remove redundant sleep 1; sync
[PATCH 3/4] Shut down the appliance cleanly
[PATCH 4/4] Ignore launch() error in virt-rescue
These were previously 2 patches. They are otherwise
2010 Aug 03
3
Generate coredumps of the guestfs appliance
[PATCH 1/3] Add a core_pattern debug command
The first patch is just a rework of Rich's earlier core dump patch. It turns it
into a debug subcommand so it can be called at any time. This also has the
advantage of explicitly labelling an extremely untidy API as debug.
[PATCH 2/3] Call sync after guestfsd exits
The second patch seems to be required for cores to be dumped reliably. I was
able to
2012 Mar 13
2
[PATCH 0/2] 'int' to 'size_t' changes
These two patches are probably not completely independent, but
separating them is a lot of work.
With *both* patches applied, all the tests and extra-tests pass.
That's no guarantee however that there isn't a mistake, so I don't
think this patch is a candidate for the 1.16 branch, until it's had a
lot more testing in development.
Rich.