[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
apparently fixed in 14.04 LTS ** Changed in: gdb (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/691814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
Launchpad has imported 6 comments from the remote bug at http://sourceware.org/bugzilla/show_bug.cgi?id=12217. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-11-13T00:53:47+00:00 Dennis Francis wrote: Created attachment 5120 Screen dump of debug procedure; Backtrace of gdb using gdb Steps to reproduce -- 1. Start gdb 2. Load and start any arbitrary binary. 3. Issue the command 'strace' without any args --- gdb segfaults ! As per GDB's internal doc (gdb) help strace Set a static tracepoint at specified line, function or marker. strace [LOCATION] [if CONDITION] . . With no LOCATION, uses current execution address of the selected stack frame Debug gdb using gdb 1. Created a simple binary trivial 2. Started gdb 3. load and run gdb 3.1. Load and start trivial 3.2. issue 'strace' command segfaults 4. run bt [See the attachment for the complete screen dump] Backtrace generated in the parent gdb after the segfault - #0 0xb7cca90d in strncmp () from /lib/libc.so.6 #1 0x08109ebd in create_breakpoint (gdbarch=0x8542578, arg=0x0, cond_string=0x0, thread=0, parse_condition_and_thread=1, tempflag=0, type_wanted=bp_static_tracepoint, ignore_count=0, pending_break_support=AUTO_BOOLEAN_AUTO, ops=0x0, from_tty=1, enabled=1) at breakpoint.c:7475 #2 0x0810f7cf in strace_command (arg=0x0, from_tty=1) at breakpoint.c:10908 #3 0x080c4beb in do_cfunc (c=0x8452368, args=0x0, from_tty=1) at ./cli/cli-decode.c:67 #4 0x080c72cb in cmd_func (cmd=0x8452368, args=0x0, from_tty=1) at ./cli/cli-decode.c:1771 #5 0x080578dd in execute_command (p=0x84309d6 , from_tty=1) at top.c:422 #6 0x0816f27a in command_handler (command=0x84309d0 strace) at event-top.c:498 #7 0x0816f7de in command_line_handler (rl=0x8511b48 \300\241X\b(\033Q\b) at event-top.c:702 #8 0x0825992b in rl_callback_read_char () at callback.c:205 #9 0x0816e9e7 in rl_callback_read_char_wrapper (client_data=0x0) at event-top.c:178 #10 0x0816f172 in stdin_event_handler (error=0, client_data=0x0) at event-top.c:433 #11 0x0816deaa in handle_file_event (data=...) at event-loop.c:817 #12 0x0816d6ed in process_event () at event-loop.c:399 #13 0x0816d7b2 in gdb_do_one_event (data=0x0) at event-loop.c:464 #14 0x0816864a in catch_errors (func=0x816d6fb gdb_do_one_event, func_args=0x0, errstring=0x832968b , mask=6) at exceptions.c:518 #15 0x080d9f48 in tui_command_loop (data=0x0) at ./tui/tui-interp.c:171 #16 0x08168d16 in current_interp_command_loop () at interps.c:291 #17 0x0804ebee in captured_command_loop (data=0x0) at ./main.c:227 #18 0x0816864a in catch_errors (func=0x804ebe3 captured_command_loop, func_args=0x0, errstring=0x830ac06 , mask=6) at exceptions.c:518 #19 0x0804fa7e in captured_main (data=0xb480) at ./main.c:910 #20 0x0816864a in catch_errors (func=0x804ec24 captured_main, func_args=0xb480, errstring=0x830ac06 , mask=6) at exceptions.c:518 #21 0x0804fab4 in gdb_main (args=0xb480) at ./main.c:919 #22 0x0804e973 in main (argc=1, argv=0xb544) at gdb.c:34 Looks like strncpy() dereferences the null pointer arg I haven't tried any previous versions for the same issue. Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/0 On 2010-11-13T01:09:28+00:00 Dennis Francis wrote: (In reply to comment #0) Looks like strncpy() dereferences the null pointer arg Correction - strncmp() ( not strncpy() ) Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/1 On 2010-11-25T23:17:08+00:00 Marc-khouzam wrote: Fix posted at http://sourceware.org/ml/gdb-patches/2010-11/msg00438.html I'm committing it now. Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/2 On 2010-11-25T23:30:17+00:00 Marc-khouzam wrote: Committed fix to HEAD and 7_2 http://sourceware.org/ml/gdb-patches/2010-11/msg00440.html Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/3 On 2010-11-25T23:33:13+00:00 Pedro-codesourcery wrote: Thanks Marc. Closing. Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/4 On 2010-12-18T15:39:47+00:00 Pedro-codesourcery wrote: *** Bug 12271 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/gdb/+bug/691814/comments/9 ** Changed in: gdb Status: Unknown = Fix Released ** Changed in: gdb
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
** Visibility changed to: Public ** Tags added: i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
There's a bug report on the upstream tracker that is *possibly* the same bug as this: http://sourceware.org/bugzilla/show_bug.cgi?id=12271 I've inquired about the details. I'm unsure whether that bug occurs only when strace is run with no arguments (in which case this is probably the same bug), or whenever strace is run. ** Bug watch added: Sourceware.org Bugzilla #12271 http://sourceware.org/bugzilla/show_bug.cgi?id=12271 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
The original reporter (calimeroteknik at free dot fr, who filed the upstream bug report) has verified that this is the same bug. ** Also affects: gdb via http://sourceware.org/bugzilla/show_bug.cgi?id=12271 Importance: Unknown Status: Unknown ** Changed in: gdb (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
That upstream bug report has been found to be a duplicate of another upstream bug report: http://sourceware.org/bugzilla/show_bug.cgi?id=12217 That bug was fixed in the upstream source last month, so I guess we just need a new downstream update for gdb in Ubuntu. ** Bug watch added: Sourceware.org Bugzilla #12217 http://sourceware.org/bugzilla/show_bug.cgi?id=12217 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
The old external bug watch (for Sourceware.org Bugzilla #12271) turned out to be an upstream duplicate -- this is the original bug report. ** Changed in: gdb Remote watch: Sourceware.org Bugzilla #12271 = Sourceware.org Bugzilla #12217 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
Sorry about the confusion -- I mean that sourceware-bugs #12217 is the original bug report, not that this Launchpad report came first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691814] Re: gdb crashed with SIGSEGV in response to strace command with no arguments
I've checked to see if this has already been fixed in the Natty git sources (lp:ubuntu/gdb) -- it has not. But the latest upstream cvs sources compile on Natty and produce the desired behavior. (For example, running gdb with no arguments and immediately running the strace command with no arguments produces the output: No default breakpoint address now.). I don't expect that any complications would arise, merging the upstream fix into the ubuntu/gdb sources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691814 Title: gdb crashed with SIGSEGV in response to strace command with no arguments -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
