public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hyrum at hyrumwright dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13619] Crash when running binary a second time in the same session Date: Tue, 07 Feb 2012 18:20:00 -0000 [thread overview] Message-ID: <bug-13619-4717-UHgni25awK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13619-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13619 --- Comment #3 from Hyrum Wright <hyrum at hyrumwright dot org> 2012-02-07 18:20:15 UTC --- Rebuilt without optimization (which, incidentally is itself non-trivial), and I now get the following stack trace: [[[ (gdb) bt #0 0x00007fff94e0e6c0 in malloc_error_break () #1 0x00007fff94e0e805 in free () #2 0x0000000100333dc2 in xfree (ptr=0x10046e998) at common-utils.c:107 #3 0x000000010020271a in gdb_bfd_unref (abfd=0x100be5e50) at objfiles.c:1557 #4 0x00000001001ff67b in free_objfile (objfile=0x10124e800) at objfiles.c:597 #5 0x0000000100200c0e in objfile_purge_solibs () at objfiles.c:986 #6 0x00000001000267b9 in no_shared_libraries (ignored=0x0, from_tty=1) at solib.c:1205 #7 0x00000001001e9fbd in target_pre_inferior (from_tty=1) at target.c:2479 #8 0x0000000100186a56 in run_command_1 (args=0x0, from_tty=1, tbreak_at_main=0) at infcmd.c:516 #9 0x0000000100186d87 in run_command (args=0x0, from_tty=1) at infcmd.c:620 #10 0x000000010007487c in do_cfunc (c=0x100b40300, args=0x0, from_tty=1) at cli-decode.c:67 #11 0x0000000100079117 in cmd_func (cmd=0x100b40300, args=0x0, from_tty=1) at cli-decode.c:1810 #12 0x00000001002eef5c in execute_command (p=0x100b0a221 "", from_tty=1) at top.c:441 #13 0x00000001001ba2ca in command_handler (command=0x100b0a220 "") at event-top.c:435 #14 0x00000001001baad3 in command_line_handler (rl=0x100becf80 "??\v\020") at event-top.c:636 #15 0x0000000100359359 in rl_callback_read_char () at callback.c:220 #16 0x00000001001b9a11 in rl_callback_read_char_wrapper (client_data=0x0) at event-top.c:169 #17 0x00000001001ba177 in stdin_event_handler (error=0, client_data=0x0) at event-top.c:375 #18 0x00000001001b883a in handle_file_event (data={ptr = 0x7fff00000000, integer = 0}) at event-loop.c:827 #19 0x00000001001b7c1e in process_event () at event-loop.c:401 #20 0x00000001001b7d1d in gdb_do_one_event () at event-loop.c:465 #21 0x00000001001b7d92 in start_event_loop () at event-loop.c:490 #22 0x00000001001b9a5b in cli_command_loop () at event-top.c:182 #23 0x00000001001ae49a in current_interp_command_loop () at interps.c:309 #24 0x00000001001af2de in captured_command_loop (data=0x0) at main.c:232 #25 0x00000001001ad51a in catch_errors (func=0x1001af2c0 <captured_command_loop>, func_args=0x0, errstring=0x100486080 "", mask=6) at exceptions.c:502 #26 0x00000001001b0a25 in captured_main (data=0x7fff5fbffa20) at main.c:942 #27 0x00000001001ad51a in catch_errors (func=0x1001af340 <captured_main>, func_args=0x7fff5fbffa20, errstring=0x100486080 "", mask=6) at exceptions.c:502 #28 0x00000001001b0bc4 in gdb_main (args=0x7fff5fbffa20) at main.c:951 #29 0x0000000100001423 in main (argc=2, argv=0x7fff5fbffa80) at gdb.c:34 ]]] It looks like the calls to gdb_bfd_unref() and xfree() were optimized out in the first version, but things are otherwise the same. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-07 18:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 17:53 [Bug gdb/13619] New: " hyrum at hyrumwright dot org 2012-01-24 18:40 ` [Bug gdb/13619] " hyrum at hyrumwright dot org 2012-02-07 16:04 ` tromey at redhat dot com 2012-02-07 18:20 ` hyrum at hyrumwright dot org [this message] 2012-02-07 19:29 ` tromey at redhat dot com 2012-02-07 19:44 ` hyrum at hyrumwright dot org 2012-02-07 21:16 ` tromey at redhat dot com 2012-02-08 15:14 ` tromey at redhat dot com 2012-02-08 16:16 ` hyrum at hyrumwright dot org 2012-02-08 16:21 ` tromey 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-13619-4717-UHgni25awK@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).