This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug threads/16216] New: auto-load safe-path warning for non-existing libthread_db.so.1


https://sourceware.org/bugzilla/show_bug.cgi?id=16216

            Bug ID: 16216
           Summary: auto-load safe-path warning for non-existing
                    libthread_db.so.1
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com
              Host: x86_64-unknown-linux-gnu
            Target: x86_64-unknown-linux-gnu

echo 'main(){}'|gcc -pthread -x c -;gdb -q -ex "set libthread-db-search-path
$PWD"':$sdir:$pdir' -ex 'show libthread-db-search-path' -ex start ./a.out 

warning: File "/tmp/libthread_db.so.1" auto-loading has been declined by your
`auto-load safe-path' set to
"$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
[...]

$ ls -l /tmp/libthread_db.so.1
ls: cannot access /tmp/libthread_db.so.1: No such file or directory

The auto-load safety violation is normally printed only after GDB has verified
it is going to load that file.  For libthread_db the auto-load safety check is
done too early.

Downstream bugreport by Carlos O'Donell:
https://bugzilla.redhat.com/show_bug.cgi?id=1034016

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]