Commit graph

123652 commits

Author SHA1 Message Date
Joel Brobecker
7adf9fa6b1 Set GDB version number to 17.2.
This commit changes gdb/version.in to 17.2.
2026-05-10 07:26:46 -07:00
GDB Administrator
e52c5d9693 Automatic date update in version.in 2026-05-10 00:00:21 +00:00
GDB Administrator
f329301345 Automatic date update in version.in 2026-05-09 00:00:20 +00:00
GDB Administrator
37b73bee5c Automatic date update in version.in 2026-05-08 00:00:20 +00:00
GDB Administrator
682f097a97 Automatic date update in version.in 2026-05-07 00:00:20 +00:00
GDB Administrator
bf9208e8cf Automatic date update in version.in 2026-05-06 00:00:22 +00:00
GDB Administrator
c48cdfdb61 Automatic date update in version.in 2026-05-05 00:00:21 +00:00
GDB Administrator
05df880d14 Automatic date update in version.in 2026-05-04 00:00:22 +00:00
GDB Administrator
45a52d0464 Automatic date update in version.in 2026-05-03 00:00:20 +00:00
GDB Administrator
da55e1b63c Automatic date update in version.in 2026-05-02 00:00:21 +00:00
GDB Administrator
effa692b5b Automatic date update in version.in 2026-05-01 00:00:20 +00:00
GDB Administrator
256da61d59 Automatic date update in version.in 2026-04-30 00:00:21 +00:00
GDB Administrator
1cfdc98e68 Automatic date update in version.in 2026-04-29 00:00:21 +00:00
Tom de Vries
063b0d3f0b [gdb/breakpoints] Don't ignore <file> in rbreak <file>:<regexp>
PR breakpoints/34112 reports that "rbreak <file>:<regexp>" sets breakpoints in
files other than <file>.

This is a regression since commit c4c093a31f ("Make
global_symbol_searcher::filenames private"), which did:
...
   if (file_name != nullptr)
-    spec.filenames.push_back (file_name);
+    spec.add_filename (std::move (file_name));
...

The std::move nullifies file_name, so a subsequent file_name check:
...
	  if (file_name != nullptr)
...
now always evaluates to false.

Fix this by:
- introducing a variable bool file_name_p, initialized before the
  std::move, and
- using that instead.

Tested on x86_64-linux.

Approved-By: Tom Tromey <tom@tromey.com>

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34112
2026-04-28 16:12:44 +02:00
GDB Administrator
7f5875a71e Automatic date update in version.in 2026-04-28 00:00:22 +00:00
GDB Administrator
368149b7e4 Automatic date update in version.in 2026-04-27 00:00:21 +00:00
GDB Administrator
4ab8e7c4a4 Automatic date update in version.in 2026-04-26 00:00:23 +00:00
GDB Administrator
f1cbe87fd6 Automatic date update in version.in 2026-04-25 00:00:22 +00:00
GDB Administrator
696d70c8ba Automatic date update in version.in 2026-04-24 00:00:21 +00:00
GDB Administrator
b3c16c9429 Automatic date update in version.in 2026-04-23 00:00:21 +00:00
GDB Administrator
a7796d1b40 Automatic date update in version.in 2026-04-22 00:00:20 +00:00
GDB Administrator
6c526f5756 Automatic date update in version.in 2026-04-21 00:00:23 +00:00
GDB Administrator
7ca056d320 Automatic date update in version.in 2026-04-20 00:00:21 +00:00
Sunil Dora
17d05df7da
gdb/ser-unix: add POSIX cfsetispeed/cfsetospeed support for custom baud rates
glibc 2.42 and later, and GNU Hurd, accept arbitrary baud rates
directly via cfsetispeed and cfsetospeed.  This behaviour is expected
to be standardized in a future POSIX revision.

Introduce a configure-time test (HAVE_CFSETSPEED_ARBITRARY) that
detects this capability and add a new platform-agnostic helper
set_custom_baudrate_posix.  The main dispatcher now prefers the POSIX
path when it is available, falling back to the existing Linux (BOTHER)
or Darwin (IOSSIOSPEED) implementations otherwise.

The HAVE_CUSTOM_BAUDRATE_SUPPORT guard is extended to also cover the
new POSIX case.

Suggested-by: Kevin Buettner <kevinb@redhat.com>
Suggested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Signed-off-by: Sunil Dora <sunilkumar.dora@windriver.com>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Approved-by: Kevin Buettner <kevinb@redhat.com>
(cherry picked from commit 7d53467645)
2026-04-19 17:30:22 +01:00
Sunil Dora
56c4ba5d7b
gdb/ser-unix: fix musl build failure when setting custom baud rates
On musl-based systems, <asm/termbits.h> may expose BOTHER even though
struct termios does not define c_ispeed/c_ospeed.  This causes the
Linux-specific custom baud rate path to be compiled and fail to build.

Fix the problem at the macro level by requiring
HAVE_STRUCT_TERMIOS_C_OSPEED (obtained via AC_CHECK_MEMBERS) together
with BOTHER in the HAVE_CUSTOM_BAUDRATE_SUPPORT guard.  This prevents
the Linux-specific code from being compiled on musl while leaving
set_custom_baudrate_linux unchanged.

This is a pure build fix with no functional or behavioural change on
any existing platform.

Suggested-by: Maciej W. Rozycki <macro@orcam.me.uk>
Signed-off-by: Sunil Dora <sunilkumar.dora@windriver.com>
Approved-by: Kevin Buettner <kevinb@redhat.com>
(cherry picked from commit 94d58b3add)
2026-04-19 17:27:35 +01:00
GDB Administrator
cbfea6fd23 Automatic date update in version.in 2026-04-19 00:00:20 +00:00
GDB Administrator
b8646c2621 Automatic date update in version.in 2026-04-18 00:00:21 +00:00
GDB Administrator
ccca9d0fbf Automatic date update in version.in 2026-04-17 00:00:21 +00:00
GDB Administrator
fc111c4cb2 Automatic date update in version.in 2026-04-16 00:00:21 +00:00
GDB Administrator
3df0379ab1 Automatic date update in version.in 2026-04-15 00:00:24 +00:00
GDB Administrator
615a703c4d Automatic date update in version.in 2026-04-14 00:00:21 +00:00
GDB Administrator
9eedc223e2 Automatic date update in version.in 2026-04-13 00:00:21 +00:00
GDB Administrator
43cfe55f0c Automatic date update in version.in 2026-04-12 00:00:21 +00:00
GDB Administrator
1d6e05b8a1 Automatic date update in version.in 2026-04-11 00:00:21 +00:00
GDB Administrator
39990e85e8 Automatic date update in version.in 2026-04-10 00:00:22 +00:00
GDB Administrator
2b7935b83c Automatic date update in version.in 2026-04-09 00:00:22 +00:00
GDB Administrator
49aff82598 Automatic date update in version.in 2026-04-08 00:00:20 +00:00
GDB Administrator
f08795df91 Automatic date update in version.in 2026-04-07 00:00:22 +00:00
GDB Administrator
55f2c84953 Automatic date update in version.in 2026-04-06 00:00:20 +00:00
GDB Administrator
95982b834c Automatic date update in version.in 2026-04-05 00:00:20 +00:00
GDB Administrator
40cb48f973 Automatic date update in version.in 2026-04-04 00:00:20 +00:00
GDB Administrator
9319777809 Automatic date update in version.in 2026-04-03 00:00:21 +00:00
GDB Administrator
2a66ab6263 Automatic date update in version.in 2026-04-02 00:00:21 +00:00
GDB Administrator
7fe55140ac Automatic date update in version.in 2026-04-01 00:00:21 +00:00
GDB Administrator
5d82c28700 Automatic date update in version.in 2026-03-31 00:00:20 +00:00
GDB Administrator
c6ad1ef140 Automatic date update in version.in 2026-03-30 00:00:20 +00:00
GDB Administrator
a2606f2651 Automatic date update in version.in 2026-03-29 00:00:19 +00:00
GDB Administrator
3304fc2535 Automatic date update in version.in 2026-03-28 00:00:20 +00:00
GDB Administrator
a80222e29f Automatic date update in version.in 2026-03-27 00:00:21 +00:00
GDB Administrator
ce5808ef7b Automatic date update in version.in 2026-03-26 00:00:20 +00:00