From: "awillia2 at sourcefire dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/23260] SystemTap usage appears to adversely affect GDB breakpoint functionality
Date: Thu, 19 Jul 2018 15:59:00 -0000 [thread overview]
Message-ID: <bug-23260-6586-b52xCKpUwi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23260-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23260
--- Comment #4 from Andrew W <awillia2 at sourcefire dot com> ---
Just to follow-up on this, the issue also affects C binaries as well, but in a
different way. For the program below:
int main()
{
return 1;
}
$ gcc main.c
$ gdb ./a.out
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
...
This GDB was configured as "x86_64-linux-gnu".
...
Reading symbols from ./a.out...(no debugging symbols found)...done.
(gdb) break _start
Breakpoint 1 at 0x4f0
(gdb) run
Starting program: /home/zelda/Desktop/a.out
Breakpoint 1, 0x00005555555544f0 in _start ()
(gdb)
[In a second terminal]
$ ps -eL -o pid,ppid,lwp,stat,nlwp,cmd | awk 'NR==1 ||
/\/home\/zelda\/Desktop\/a.out/'
PID PPID LWP STAT NLWP CMD
56346 56342 56346 t 1 /home/zelda/Desktop/a.out
$ sudo stap --suppress-handler-errors --skip-badvars strace.stp -x 56346 -v
Pass 1: parsed user script and 465 library scripts using
119616virt/48552res/6432shr/42428data kb, in 90usr/90sys/286real ms.
Pass 2: analyzed script: 1116 probes, 207 functions, 104 embeds, 108 globals
using 311348virt/239224res/5376shr/234160data kb, in 22240usr/1320sys/26099real
ms.
Pass 3: using cached
/home/zelda/.systemtap/cache/02/stap_027e862ab47a5cdf6a07ae0b1c596ae7_1079724.c
Pass 4: using cached
/home/zelda/.systemtap/cache/02/stap_027e862ab47a5cdf6a07ae0b1c596ae7_1079724.ko
Pass 5: starting run.
Thu Jul 19 15:47:35 2018.405124 exit_group(1) =
[ In a third terminal, you can see the process is no longer running ]
$ ps -eL -o pid,ppid,lwp,stat,nlwp,cmd | awk 'NR==1 ||
/\/home\/zelda\/Desktop\/a.out/'
PID PPID LWP STAT NLWP CMD
$
[ In the first terminal ]
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint 1.
Cannot access memory at address 0x5555555544f0
Cannot insert breakpoint -2.
Temporarily disabling shared library breakpoints:
breakpoint #-2
breakpoint #-5
breakpoint #-7
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-07-19 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 18:06 [Bug kprobes/23260] New: " awillia2 at sourcefire dot com
2018-06-05 18:08 ` [Bug kprobes/23260] " awillia2 at sourcefire dot com
2018-06-06 17:58 ` fche at redhat dot com
2018-06-08 22:01 ` awillia2 at sourcefire dot com
2018-07-19 15:59 ` awillia2 at sourcefire dot com [this message]
2018-07-25 20:50 ` fche at redhat dot com
2020-02-19 21:10 ` fche at redhat dot com
2020-07-09 18:34 ` amerey at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-23260-6586-b52xCKpUwi@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).