{"push_id":750221093,"size":63,"distinct_size":63,"ref":"refs/heads/cxx-01","head":"1b859204e8a4e5f8368ec3855c85ddcc0f2adfd8","before":"2faecb5169fffc9e76b6ff3c9fde786348b48d4c","commits":[{"sha":"0cf003f49ee8bbd5dc5f1ce45193c7ae056c69b8","author":{"email":"46ff6e41b02a6ff6bd50cc64faab96b75208d63d@sourceware.org","name":"GDB Administrator"},"message":"Automatic date update in version.in","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/0cf003f49ee8bbd5dc5f1ce45193c7ae056c69b8"},{"sha":"e0a3af227ee0602ae69320fd6f931c363f14975b","author":{"email":"64b285df2af30b39a5c8967bdd7812e31d1a9397@gmail.com","name":"Alan Modra"},"message":"Revert ALIGN changes\n\nReverts a2c59f28 and e474ab13.  Since the unary form of ALIGN only\nreferences \"dot\" implicitly, there isn't really a strong argument for\nmaking ALIGN use a relative value when inside an output section.\n\n\t* ldexp.c (align_dot_val): Delete.\n\t(fold_unary <ALIGN_K, NEXT>): Revert 2015-07-10 change.\n\t(is_align_conditional): Revert 2015-07-20 change.\n\t(exp_fold_tree_1): Likewise, but keep expanded comment.\n\t* scripttempl/elf.sc (.ldata, .bss): Revert 2015-07-20 change.\n\t* ld.texinfo (<ALIGN>): Correct description.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/e0a3af227ee0602ae69320fd6f931c363f14975b"},{"sha":"ad071a3055b9b47dad340c1a1cb3a9b39529cef0","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"Linux gdbserver fork event debug output\n\nThe \"extended event with waitstatus\" debug output is unreachable, as\nit is guarded by \"if (!report_to_gdb)\".  If extended_event_reported is\ntrue, then so is report_to_gdb.  Move it to where we print why we're\nreporting an event to GDB.\n\nAlso, the debug output currently tries to print the wrong struct\ntarget_waitstatus.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* linux-low.c (linux_wait_1): Move fork event output out of the\n\t!report_to_gdb check.  Pass event_child->waitstatus to\n\ttarget_waitstatus_to_string instead of ourstatus.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/ad071a3055b9b47dad340c1a1cb3a9b39529cef0"},{"sha":"00db26facc14ac830adef704bba9b24d0d366ddf","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"Linux gdbserver confused when event randomization picks process exit event\n\nThe tail end of linux_wait_1 isn't expecting that the select_event_lwp\nmachinery can pick a whole-process exit event to report to GDB.  When\nthat happens, both gdb and gdbserver end up quite confused:\n\n ...\n (gdb)\n [Thread 24971.24971] #1 stopped.\n 0x0000003615a011f0 in ?? ()\n c&\n Continuing.\n (gdb) [New Thread 24971.24981]\n [New Thread 24983.24983]\n [New Thread 24971.24982]\n\n [Thread 24983.24983] #3 stopped.\n 0x0000003615ebc7cc in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/fork.c:130\n 130       pid = ARCH_FORK ();\n [New Thread 24984.24984]\n Error in re-setting breakpoint -16: PC register is not available\n Error in re-setting breakpoint -17: PC register is not available\n Error in re-setting breakpoint -18: PC register is not available\n Error in re-setting breakpoint -19: PC register is not available\n Error in re-setting breakpoint -24: PC register is not available\n Error in re-setting breakpoint -25: PC register is not available\n Error in re-setting breakpoint -26: PC register is not available\n Error in re-setting breakpoint -27: PC register is not available\n Error in re-setting breakpoint -28: PC register is not available\n Error in re-setting breakpoint -29: PC register is not available\n Error in re-setting breakpoint -30: PC register is not available\n PC register is not available\n (gdb)\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* linux-low.c (add_lwp): Set waitstatus to TARGET_WAITKIND_IGNORE.\n\t(linux_thread_alive): Use lwp_is_marked_dead.\n\t(extended_event_reported): Delete.\n\t(linux_wait_1): Check if waitstatus is TARGET_WAITKIND_IGNORE\n\tinstead of extended_event_reported.\n\t(mark_lwp_dead): Don't set the 'dead' flag.  Store the waitstatus\n\tas well.\n\t(lwp_is_marked_dead): New function.\n\t(lwp_running): Use lwp_is_marked_dead.\n\t* linux-low.h: Delete 'dead' field, and update 'waitstatus's\n\tcomment.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/00db26facc14ac830adef704bba9b24d0d366ddf"},{"sha":"863d01bde2725d009c45ab7e9ba1dbf3f5b923f8","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"gdbserver: Fix non-stop / fork / step-over issues\n\nRef: https://sourceware.org/ml/gdb-patches/2015-07/msg00868.html\n\nThis adds a test that has a multithreaded program have several threads\ncontinuously fork, while another thread continuously steps over a\nbreakpoint.\n\nThis exposes several intertwined issues, which this patch addresses:\n\n - When we're stopping and suspending threads, some thread may fork,\n   and we missed setting its suspend count to 1, like we do when a new\n   clone/thread is detected.  When we next unsuspend threads, the fork\n   child's suspend count goes below 0, which is bogus and fails an\n   assertion.\n\n - If a step-over is cancelled because a signal arrives, but then gdb\n   is not interested in the signal, we pass the signal straight back\n   to the inferior.  However, we miss that we need to re-increment the\n   suspend counts of all other threads that had been paused for the\n   step-over.  As a result, other threads indefinitely end up stuck\n   stopped.\n\n - If a detach request comes in just while gdbserver is handling a\n   step-over (in the test at hand, this is GDB detaching the fork\n   child), gdbserver internal errors in stabilize_thread's helpers,\n   which assert that all thread's suspend counts are 0 (otherwise we\n   wouldn't be able to move threads out of the jump pads).  The\n   suspend counts aren't 0 while a step-over is in progress, because\n   all threads but the one stepping past the breakpoint must remain\n   paused until the step-over finishes and the breakpoint can be\n   reinserted.\n\n - Occasionally, we see \"BAD - reinserting but not stepping.\" being\n   output (from within linux_resume_one_lwp_throw).  That was because\n   GDB pokes memory while gdbserver is busy with a step-over, and that\n   suspends threads, and then re-resumes them with proceed_one_lwp,\n   which missed another reason to tell linux_resume_one_lwp that the\n   thread should be set back to stepping.\n\n - In a couple places, we were resuming threads that are meant to be\n   suspended.  E.g., when a vCont;c/s request for thread B comes in\n   just while gdbserver is stepping thread A past a breakpoint.  The\n   resume for thread B must be deferred until the step-over finishes.\n\n - The test runs with both \"set detach-on-fork\" on and off.  When off,\n   it exercises the case of GDB detaching the fork child explicitly.\n   When on, it exercises the case of gdb resuming the child\n   explicitly.  In the \"off\" case, gdb seems to exponentially become\n   slower as new inferiors are created.  This is _very_ noticeable as\n   with only 100 inferiors gdb is crawling already, which makes the\n   test take quite a bit to run.  For that reason, I've disabled the\n   \"off\" variant for now.\n\ngdb/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* target/waitstatus.h (enum target_stop_reason)\n\t<TARGET_STOPPED_BY_SINGLE_STEP>: New value.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* linux-low.c (handle_extended_wait): Set the fork child's suspend\n\tcount if stopping and suspending threads.\n\t(check_stopped_by_breakpoint): If stopped by trace, set the LWP's\n\tstop reason to TARGET_STOPPED_BY_SINGLE_STEP.\n\t(linux_detach): Complete an ongoing step-over.\n\t(lwp_suspended_inc, lwp_suspended_decr): New functions.  Use\n\tthroughout.\n\t(resume_stopped_resumed_lwps): Don't resume a suspended thread.\n\t(linux_wait_1): If passing a signal to the inferior after\n\tfinishing a step-over, unsuspend and re-resume all lwps.  If we\n\tsee a single-step event but the thread should be continuing, don't\n\tpass the trap to gdb.\n\t(stuck_in_jump_pad_callback, move_out_of_jump_pad_callback): Use\n\tinternal_error instead of gdb_assert.\n\t(enqueue_pending_signal): New function.\n\t(check_ptrace_stopped_lwp_gone): Add debug output.\n\t(start_step_over): Use internal_error instead of gdb_assert.\n\t(complete_ongoing_step_over): New function.\n\t(linux_resume_one_thread): Don't resume a suspended thread.\n\t(proceed_one_lwp): If the LWP is stepping over a breakpoint, reset\n\tit stepping.\n\ngdb/testsuite/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* gdb.threads/forking-threads-plus-breakpoint.exp: New file.\n\t* gdb.threads/forking-threads-plus-breakpoint.c: New file.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/863d01bde2725d009c45ab7e9ba1dbf3f5b923f8"},{"sha":"b6b9ffccac04b8729d5206b5a9fefa09ea2510f3","author":{"email":"849534a30cbb3e3ef3ecefba82412891f1aaeb01@arm.com","name":"Pierre Langlois"},"message":"Remove required field in agent's symbols\n\nThis field was never set nor used.  This patch removes it.\n\ngdb/ChangeLog:\n\n\t* common/agent.c (symbol_list) <required>: Remove.\n\ngdb/gdbserver/ChangeLog:\n\n\t* tracepoint.c (symbol_list) <required>: Remove.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/b6b9ffccac04b8729d5206b5a9fefa09ea2510f3"},{"sha":"4807d3f32937bc4d932638fd8f8b3084be82b74a","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"test slowdown","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/4807d3f32937bc4d932638fd8f8b3084be82b74a"},{"sha":"83e97ed023e828a7d924b765661374272c7f7eb4","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"Test for PR18749: problems if whole process dies while (ptrace-) stopped\n\nThis adds a kfailed test that has the whole process exit just while\nseveral threads continuously step over a breakpoint.  Usually, the\nprocess exits just while GDB or GDBserver is handling the breakpoint\nhit.  In other words, the process disappears while the event thread is\n(ptrace-) stopped.  This exposes several issues in GDB and GDBserver.\nErrors, crashes, etc.\n\nI fixed some of these issues recently, but there's a lot more to do.\nIt's a bit like playing whack-a-mole at the moment.  You fix an issue,\nwhich then exposes several others.\n\nE.g., with the native target, you get (among other errors):\n\n  (...)\n  [New Thread 0x7ffff47b9700 (LWP 18077)]\n  [New Thread 0x7ffff3fb8700 (LWP 18078)]\n  [New Thread 0x7ffff37b7700 (LWP 18079)]\n  Cannot find user-level thread for LWP 18076: generic error\n  (gdb) KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited (prompt) (PRMS: gdb/18749)\n\ngdb/testsuite/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\tPR gdb/18749\n\t* gdb.threads/process-dies-while-handling-bp.c: New file.\n\t* gdb.threads/process-dies-while-handling-bp.exp: New file.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/83e97ed023e828a7d924b765661374272c7f7eb4"},{"sha":"f6a9d9c7db9b6b58e6915869c1bd7c83d96d31ee","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"Revert \"test slowdown\"\n\nThat was pushed by mistake.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/f6a9d9c7db9b6b58e6915869c1bd7c83d96d31ee"},{"sha":"bf47e2482d3e88580ba5a22db48bc773fa8ced3f","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"Fix gdbserver --debug issues caught by Valgrind\n\nRunning gdbserver --debug under Valgrind shows:\n\n ==4803== Invalid read of size 4\n ==4803==    at 0x432B62: linux_write_memory (linux-low.c:5320)\n ==4803==    by 0x4143F7: write_inferior_memory (target.c:83)\n ==4803==    by 0x415895: remove_memory_breakpoint (mem-break.c:362)\n ==4803==    by 0x432EF5: linux_remove_point (linux-low.c:5460)\n ==4803==    by 0x416319: delete_raw_breakpoint (mem-break.c:802)\n ==4803==    by 0x4163F3: release_breakpoint (mem-break.c:842)\n ==4803==    by 0x416477: delete_breakpoint_1 (mem-break.c:869)\n ==4803==    by 0x4164EF: delete_breakpoint (mem-break.c:891)\n ==4803==    by 0x416843: delete_gdb_breakpoint_1 (mem-break.c:1069)\n ==4803==    by 0x4168D8: delete_gdb_breakpoint (mem-break.c:1098)\n ==4803==    by 0x4134E3: process_serial_event (server.c:4051)\n ==4803==    by 0x4138E4: handle_serial_event (server.c:4196)\n ==4803==  Address 0x4c6b930 is 0 bytes inside a block of size 1 alloc'd\n ==4803==    at 0x4A0645D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)\n ==4803==    by 0x4240C6: xmalloc (common-utils.c:43)\n ==4803==    by 0x41439C: write_inferior_memory (target.c:80)\n ==4803==    by 0x415895: remove_memory_breakpoint (mem-break.c:362)\n ==4803==    by 0x432EF5: linux_remove_point (linux-low.c:5460)\n ==4803==    by 0x416319: delete_raw_breakpoint (mem-break.c:802)\n ==4803==    by 0x4163F3: release_breakpoint (mem-break.c:842)\n ==4803==    by 0x416477: delete_breakpoint_1 (mem-break.c:869)\n ==4803==    by 0x4164EF: delete_breakpoint (mem-break.c:891)\n ==4803==    by 0x416843: delete_gdb_breakpoint_1 (mem-break.c:1069)\n ==4803==    by 0x4168D8: delete_gdb_breakpoint (mem-break.c:1098)\n ==4803==    by 0x4134E3: process_serial_event (server.c:4051)\n ==4803==\n\nAnd:\n\n ==7272== Conditional jump or move depends on uninitialised value(s)\n ==7272==    at 0x3615E48361: vfprintf (vfprintf.c:1634)\n ==7272==    by 0x414E89: debug_vprintf (debug.c:60)\n ==7272==    by 0x42800A: debug_printf (common-debug.c:35)\n ==7272==    by 0x43937B: my_waitpid (linux-waitpid.c:149)\n ==7272==    by 0x42D740: linux_wait_for_event_filtered (linux-low.c:2441)\n ==7272==    by 0x42DADA: linux_wait_for_event (linux-low.c:2552)\n ==7272==    by 0x42E165: linux_wait_1 (linux-low.c:2860)\n ==7272==    by 0x42F5D8: linux_wait (linux-low.c:3453)\n ==7272==    by 0x4144A4: mywait (target.c:107)\n ==7272==    by 0x413969: handle_target_event (server.c:4214)\n ==7272==    by 0x41A1A6: handle_file_event (event-loop.c:429)\n ==7272==    by 0x41996D: process_event (event-loop.c:184)\n\ngdb/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* nat/linux-waitpid.c (my_waitpid): Only print *status if waitpid\n\treturned > 0.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* linux-low.c (linux_write_memory): Rewrite debug output to avoid\n\treading beyond the passed in buffer length.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/bf47e2482d3e88580ba5a22db48bc773fa8ced3f"},{"sha":"f0ce0d3a331129309a46a6a9ac85fce35acae72b","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"gdbserver: move_out_of_jump_pad_callback misses switching current thread\n\nWhile hacking on the fix for PR threads/18600 (Threads left stopped\nafter fork+thread spawn), I once saw its test (fork-plus-threads.exp)\nFAIL against gdbserver because move_out_of_jump_pad_callback has a\ngdb_breakpoint_here call, and the caller isn't making sure the current\nthread points to the right thread.  In the case I saw, the current\nthread pointed to the wrong process, so gdb_breakpoint_here returned\nthe wrong answer.  Unfortunately I didn't save logs.  Still, seems\nobvious enough and it should fix a potential occasional racy FAIL.\n\nTested on x86_64 Fedora 20.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* linux-low.c (move_out_of_jump_pad_callback): Temporarily switch\n\tthe current thread.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/f0ce0d3a331129309a46a6a9ac85fce35acae72b"},{"sha":"05d999b0896ab6ccd4ce23a715765484c60a967d","author":{"email":"fa7054fed17d58b06d3b1bf9b1077e42165a09ec@ericsson.com","name":"Simon Marchi"},"message":"Change type of struct complaints::series\n\nFound while processing the C++ enum changes.  It seems like series\nshould be of type enum complaint_series, instead of adding a cast.\n\nRedundant and out of date comments are also removed.\n\ngdb/ChangeLog:\n\n\t* complaints.c (enum complaint_series): Add newlines and remove\n\tout of date comment.\n\t(struct complaints) <series>: Change type to enum\n\tcomplaint_series and remove out of date comment.\n\t(symfile_complaint_hook): Use equivalent enum value\n\tISOLATED_MESSAGE instead of 0.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/05d999b0896ab6ccd4ce23a715765484c60a967d"},{"sha":"608a1e46394e9df951968c9112fbec3065da5fba","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"gdbserver: fix silent error exit\n\nRunning gdb.threads/process-dies-while-handling-bp.exp against\ngdbserver sometimes FAILs because GDBserver drops the connection, but\nthe logs leave no clue on what the reason could be.  Running manually\na few times, I saw the same:\n\n $  ./gdbserver/gdbserver --multi :9999 testsuite/gdb.threads/process-dies-while-handling-bp\n Process testsuite/gdb.threads/process-dies-while-handling-bp created; pid = 12766\n Listening on port 9999\n Remote debugging from host 127.0.0.1\n Listening on port 9999\n\n Child exited with status 0\n\n Child exited with status 0\n\nWhat happened is that an exception escaped and gdbserver reopened the\nconnection, which led to that second \"Listening on port 9999\" output.\n\nThe error was a failure to access registers from a now-dead thread.\nThe exception probably shouldn't have escaped here, but meanwhile,\nthis at least makes the issue less mysterious.\n\nTested on x86_64 Fedora 20.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* server.c (captured_main): On error, print the exception message\n\tto stderr, and if run_once is set, throw a quit.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/608a1e46394e9df951968c9112fbec3065da5fba"},{"sha":"ca0a5f0bd33d0aa17a5cf518e41e47ddfde486ad","author":{"email":"1a04c6012571fb0623d9126339aaaf75d21bf4d0@acm.org","name":"Clem Dickey"},"message":"PR python/17136\n\ngdb/ChangeLog:\n\n\t* python/lib/gdb/command/type_printers.py (InfoTypePrinter): Fix typo.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/ca0a5f0bd33d0aa17a5cf518e41e47ddfde486ad"},{"sha":"a44892be35506471a53e5bc8c2def4ffccf451f9","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"gdbserver: no point in hiding the regcache type nowadays\n\nThe regcache used to be hidden inside inferiors.c, but since the\ntracepoints support that it's a first class object.  This also fixes a\nfew implicit pointer conversion errors in C++ mode, caused by a few\nplaces missing the explicit cast.\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* gdbthread.h (struct regcache): Forward declare.\n\t(struct thread_info) <regcache_data>: Now a struct regcache\n\tpointer.\n\t* inferiors.c (inferior_regcache_data)\n\t(set_inferior_regcache_data): Now work with struct regcache\n\tpointers.\n\t* inferiors.h (struct regcache): Forward declare.\n\t(inferior_regcache_data, set_inferior_regcache_data): Now work\n\twith struct regcache pointers.\n\t* regcache.c (get_thread_regcache, regcache_invalidate_thread)\n\t(free_register_cache_thread): Remove struct regcache pointer\n\tcasts.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/a44892be35506471a53e5bc8c2def4ffccf451f9"},{"sha":"33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"gdbserver/tracepoint.c: make exported IPA global int instead of enum\n\nFixes another C++ -fpermissive error:\n\n  src/gdb/gdbserver/tracepoint.c:4535:21: error: invalid conversion from ‘int’ to ‘eval_result_type’ [-fpermissive]\n    expr_eval_result = ipa_expr_eval_result;\n\ngdb/gdbserver/ChangeLog:\n2015-08-06  Pedro Alves  <palves@redhat.com>\n\n\t* tracepoint.c (expr_eval_result): Now an int.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/33ebda9d6841e18d9ef18b94c3dcad7d0498ab3d"},{"sha":"e7b237fde22cf6b8b51f85a7089bd6ac62e4a26f","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"C++: Initialize a couple const globals\n\nIn C++ mode, we get:\n\n src/gdb/gdbserver/tdesc.c:43:33: error: uninitialized const ‘default_description’ [-fpermissive]\n  static const struct target_desc default_description;\n\t\t\t\t  ^\n In file included from src/gdb/gdbserver/tdesc.c:19:0:\n src/gdb/gdbserver/tdesc.h:26:8: note: ‘const struct target_desc’ has no user-provided default constructor\n  struct target_desc\n\t ^\n\ngdb/ChangeLog:\n2015-07-11  Pedro Alves  <palves@redhat.com>\n\n\t* frame.c (null_frame_id): Explicitly zero-initialize.\n\ngdb/gdbserver/ChangeLog:\n2015-07-11  Pedro Alves  <palves@redhat.com>\n\n\t* tdesc.c (default_description): Explicitly zero-initialize.","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/e7b237fde22cf6b8b51f85a7089bd6ac62e4a26f"},{"sha":"34ac3f5556b9313f3fdc9ee64e0e235b3d927b31","author":{"email":"fa7054fed17d58b06d3b1bf9b1077e42165a09ec@ericsson.com","name":"Simon Marchi"},"message":"int to enum conversion casts","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/34ac3f5556b9313f3fdc9ee64e0e235b3d927b31"},{"sha":"3bcbdb4181be64ba0879cab1d8570ab5d85b27e6","author":{"email":"fa7054fed17d58b06d3b1bf9b1077e42165a09ec@ericsson.com","name":"Simon Marchi"},"message":"Rest of enum casts","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/3bcbdb4181be64ba0879cab1d8570ab5d85b27e6"},{"sha":"fcc86d9711c214954e9f7d664b03b5a8ef716785","author":{"email":"c495fe4dba026c81f120733ccce155c132d5c6ba@redhat.com","name":"Pedro Alves"},"message":"ax_raw_byte","distinct":true,"url":"https://api.github.com/repos/simark/binutils-gdb/commits/fcc86d9711c214954e9f7d664b03b5a8ef716785"}]}