問題描述

每次 gdb 捕獲異常時，我都會收到一個煩人的錯誤.我已經運行了以下示例程序

#include int main() {拋出 std::invalid_argument("");返回0；}

運行 gdb 的結果是

 在拋出一個 'std::invalid_argument' 實例后調用終止什么():程序收到信號 SIGABRT，中止.__GI_raise (sig=sig@entry=6) 在 ../sysdeps/unix/sysv/linux/raise.c:5151 ../sysdeps/unix/sysv/linux/raise.c:沒有這樣的文件或目錄.

這還不算太糟，因為我確實得到了我需要的信息，只是讓我煩惱...

有人知道如何解決這個問題嗎?

要在 Ubuntu 上對 C 庫進行完整的源代碼調試，只需幾個步驟:

1. 安裝 libc6 的 debuginfo 版本.

   它可能已經安裝 - Ubuntu 上的 gdb 軟件包依賴于它 - 但如果沒有，請運行 sudo apt install libc6-dbg.

2. 準備包系統以下載和處理源代碼包(如果之前尚未完成).

   sudo apt install dpkg-devgrep deb-src/etc/apt/sources.list

   复制代码

   Grep 的輸出應該顯示(并且可能還有我們不需要擔心的其他匹配項):

   <塊引用>

   deb-src http://archive.ubuntu.com/ubuntu/bionic main 受限deb-src http://archive.ubuntu.com/ubuntu/bionic-updates main 受限

   复制代码

   如果 grep 顯示這些 deb-src 行用 # 注釋掉:

   <塊引用>

   # deb-src http://archive.ubuntu.com/ubuntu/bionic main 受限# deb-src http://archive.ubuntu.com/ubuntu/bionic-updates main 受限

   复制代码

   然后編輯/etc/apt/sources.list刪除這些行開頭的#，然后運行sudo apt update.

3. 下載與安裝的C庫版本對應的源代碼.

   首先，在任何地方創建一個目錄 - 我將在這里使用 /opt/src.

   然后執行以下操作:

   cd/opt/srcapt源libc6

   复制代码

   如果 apt 命令給出類似

   的錯誤信息<塊引用>

   E:您必須在您的 sources.list 中放入一些源"URI

   那么我在第 2 步中的說明可能已經過時了；在這里發表評論.

   下載完成后，運行:

   find $PWD -maxdepth 1 -type d -name 'glibc*'

   复制代码

   記住這個名字 - 它類似于 /opt/src/glibc-2.23

4. 確定 gdb 希望在哪里找到源代碼并進行適當的調整.

   運行 gdb，讓它運行你的程序直到它停止，然后在 gdb 提示符下執行以下操作:

   (gdb) 信息源當前源文件是 ../sysdeps/unix/sysv/linux/raise.c編譯目錄為/build/glibc-KM3i_a/glibc-2.23/signal

   复制代码

   所以 gdb 期望源代碼在 /build/glibc-KM3i_a/glibc-2.23 中.有兩種方法可以解決此問題:

   • 移動(或使用符號鏈接)使源代碼位于(或看起來)位于 /build/glibc-KM3i_a/glibc-2.23 中.

     或者

   • 告訴 gdb 如何替換正確的源目錄路徑名:

     (gdb) 設置替代路徑/build/glibc-KM3i_a/glibc-2.23/opt/src/glibc-2.23

     复制代码

   現在，回到你的框架，gdb 應該顯示源代碼行:

   (gdb) 第 1 幀#1 0xb7e2fea9 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54返回 INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);

   复制代码

I'm getting an an annoying error every time gdb catches an exception. I've run the following example program

#include <stdexcept>

int main() {
  throw std::invalid_argument("");
  return 0;
}

And the result from running gdb is

terminate called after throwing an instance of 'std::invalid_argument'
  what():  

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

It's not all that bad, as I do get the information I need, it's just bugging me...

Do anyone know how to fix this?

To do full source code debugging of the C library on Ubuntu, there are just a few steps to take:

1. Install the debuginfo version of libc6.

   It's probably already installed - the gdb package on Ubuntu has a dependency on it - but in case it isn't, run sudo apt install libc6-dbg.

2. Prepare the package system to download and process source code packages, if this hasn't previously been done.

   sudo apt install dpkg-dev
   grep deb-src /etc/apt/sources.list
   

   复制代码

   Grep's output should show (and there may be additional matches that we don't need to worry about):

   deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted
   deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
   

   复制代码

   If the grep shows that these deb-src lines are commented out with #:

   # deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted
   # deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
   

   复制代码

   then edit /etc/apt/sources.list to remove the # at the beginning of these lines and then run sudo apt update .

3. Download the source code corresponding to the installed version of the C library.

   First, create a directory anywhere - I'll use /opt/src here.

   Then do the following:

   cd /opt/src
   apt source libc6
   

   复制代码

   If the apt command gives an error message like

   E: You must put some 'source' URIs in your sources.list

   then my instructions in step 2 may have become outdated; post a comment here.

   When the download is complete, run this:

   find $PWD -maxdepth 1 -type d -name 'glibc*'
   

   复制代码

   Remember this name - it'll be something like /opt/src/glibc-2.23

4. Determine where gdb expects to find the source code and make appropriate adjustments.

   Run gdb, have it run your program until it stops, and at the gdb prompt do this:

   (gdb) info source
   Current source file is ../sysdeps/unix/sysv/linux/raise.c
   Compilation directory is /build/glibc-KM3i_a/glibc-2.23/signal
   

   复制代码

   So gdb is expecting the source code to be in /build/glibc-KM3i_a/glibc-2.23 . There are two ways to fix this:

   • Move (or use a symlink) so that the source code is (or appears to be) in /build/glibc-KM3i_a/glibc-2.23 .

     or

   • Tell gdb how to substitute the correct source directory pathname:

     (gdb) set substitute-path /build/glibc-KM3i_a/glibc-2.23 /opt/src/glibc-2.23
     

     复制代码

   Now, go back to your frame, and gdb should show the source code line:

   (gdb) frame 1
   #1 0xb7e2fea9 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
            return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
   

   复制代码

這篇關于GDB 抱怨缺少 raise.c的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！