From 98b45e30a6d0aae321f140d66f39cab5cb17df38 Mon Sep 17 00:00:00 2001
From: Daniel Jacobowitz <drow@false.org>
Date: Sun, 5 Jan 2003 02:03:57 +0000
Subject: * gdb.texinfo (Controlling GDB): Document "set osabi".
---
gdb/doc/ChangeLog | 4 ++++
gdb/doc/gdb.texinfo | 23 +++++++++++++++++++++++
2 files changed, 27 insertions(+)
(limited to 'gdb/doc')
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index a24ee2f..b5884d7 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,5 +1,9 @@
2003-01-04 Daniel Jacobowitz <drow@mvista.com>
+ * gdb.texinfo (Controlling GDB): Document "set osabi".
+
+2003-01-04 Daniel Jacobowitz <drow@mvista.com>
+
* gdb.texinfo (Backtraces): Document "set backtrace-below-main".
* gdbint.texinfo (FRAME_CHAIN_VALID): Update documentation.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0f7ed9f..4ad5dbe 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -12531,6 +12531,29 @@ application automatically. However, sometimes you need to override its
conclusions. Use these commands to manage @value{GDBN}'s view of the
current ABI.
+@cindex OS ABI
+@kindex set osabi
+
+One @value{GDBN} configuration can debug binaries for multiple operating
+system targets, either via remote debugging or native emulation.
+@value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use,
+but you can override its conclusion using the @code{set osabi} command.
+One example where this is useful is in debugging of binaries which use
+an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does
+not have the same identifying marks that the standard C library for your
+platform provides.
+
+@table @code
+@item show osabi
+Show the OS ABI currently in use.
+
+@item set osabi
+With no argument, show the list of registered available OS ABI's.
+
+@item set osabi @var{abi}
+Set the current OS ABI to @var{abi}.
+@end table
+
@cindex float promotion
@kindex set coerce-float-to-double
--
cgit v1.1