public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27681] FAIL: gdb.base/help.exp: apropos \(print[^[ bsiedf\".-]\) (timeout)
Date: Thu, 01 Apr 2021 09:50:48 +0000	[thread overview]
Message-ID: <bug-27681-4717-ZCMypQXC4y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27681-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27681

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
^C
Thread 1 "gdb" received signal SIGINT, Interrupt.
futex_wait (private=0, expected=2, futex_word=0x1840b78)
    at ../sysdeps/nptl/futex-internal.h:146
146       int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
(gdb) bt
#0  futex_wait (private=0, expected=2, futex_word=0x1840b78)
    at ../sysdeps/nptl/futex-internal.h:146
#1  __lll_lock_wait_private (futex=futex@entry=0x1840b78) at
./lowlevellock.c:35
#2  0x00007ffff73ef84f in re_search_stub (bufp=0x7fffffffd4c0, string=0xf8d01f
"+", 
    length=1, start=0, range=<optimized out>, stop=1, regs=0x0, ret_len=false)
    at regexec.c:390
#3  0x00007ffff73efe54 in __re_search (bufp=<optimized out>, string=<optimized
out>, 
    length=<optimized out>, start=<optimized out>, range=<optimized out>, 
    regs=<optimized out>) at regexec.c:289
#4  0x000000000070af57 in compiled_regex::search (this=0x7fffffffd4c0, 
    string=0xf8d01f "+", length=1, start=0, range=1, regs=0x0)
    at /data/gdb_versions/devel/src/gdb/gdb_regex.c:56
#5  0x00000000005877d9 in apropos_cmd (stream=0x18bd490, commandlist=0x18289d0, 
    verbose=false, regex=..., prefix=0xe7aab1 "")
    at /data/gdb_versions/devel/src/gdb/cli/cli-decode.c:1167
#6  0x0000000000580cb9 in apropos_command (
    arg=0x7fffffffe1ab "\\(print[^[ bsiedf\".-]\\)", from_tty=0)
    at /data/gdb_versions/devel/src/gdb/cli/cli-cmds.c:1639
#7  0x0000000000585e06 in do_const_cfunc (c=0x1829360, 
    args=0x7fffffffe1ab "\\(print[^[ bsiedf\".-]\\)", from_tty=0)
    at /data/gdb_versions/devel/src/gdb/cli/cli-decode.c:101
#8  0x0000000000589bd5 in cmd_func (cmd=0x1829360, 
    args=0x7fffffffe1ab "\\(print[^[ bsiedf\".-]\\)", from_tty=0)
    at /data/gdb_versions/devel/src/gdb/cli/cli-decode.c:2181
#9  0x0000000000a9ae89 in execute_command (p=0x7fffffffe1c1 ")", from_tty=0)
    at /data/gdb_versions/devel/src/gdb/top.c:670
#10 0x0000000000806a16 in catch_command_errors (
    command=0xa9a918 <execute_command(char const*, int)>, 
    arg=0x7fffffffe1a3 "apropos \\(print[^[ bsiedf\".-]\\)", from_tty=0, 
    do_bp_actions=true) at /data/gdb_versions/devel/src/gdb/main.c:450
#11 0x0000000000806beb in execute_cmdargs (cmdarg_vec=0x7fffffffd920, 
    file_type=CMDARG_FILE, cmd_type=CMDARG_COMMAND, ret=0x7fffffffd8fc)
    at /data/gdb_versions/devel/src/gdb/main.c:539
#12 0x0000000000807e4f in captured_main_1 (context=0x7fffffffdb20)
    at /data/gdb_versions/devel/src/gdb/main.c:1211
#13 0x0000000000808036 in captured_main (data=0x7fffffffdb20)
    at /data/gdb_versions/devel/src/gdb/main.c:1232
#14 0x00000000008080a1 in gdb_main (args=0x7fffffffdb20)
    at /data/gdb_versions/devel/src/gdb/main.c:1257
#15 0x000000000041781d in main (argc=10, argv=0x7fffffffdc38)
    at /data/gdb_versions/devel/src/gdb/gdb.c:32

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-04-01  9:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  9:46 [Bug gdb/27681] New: " vries at gcc dot gnu.org
2021-04-01  9:50 ` vries at gcc dot gnu.org [this message]
2021-04-01 10:06 ` [Bug gdb/27681] " vries at gcc dot gnu.org
2021-04-01 10:08 ` vries at gcc dot gnu.org
2021-04-01 11:38 ` vries at gcc dot gnu.org
2021-04-01 12:53 ` tromey at sourceware dot org
2021-04-01 13:16 ` vries at gcc dot gnu.org
2021-04-01 14:53 ` vries at gcc dot gnu.org
2021-04-02 11:17 ` vries at gcc dot gnu.org
2021-04-02 11:32 ` vries at gcc dot gnu.org
2021-04-03 13:08 ` vries at gcc dot gnu.org
2021-04-04  2:21 ` vries at gcc dot gnu.org
2021-04-06  8:53 ` schwab@linux-m68k.org
2021-04-06  9:00 ` vries at gcc dot gnu.org
2021-04-06  9:23 ` schwab@linux-m68k.org
2021-04-06 13:17 ` vries at gcc dot gnu.org
2021-04-06 14:03 ` matz at suse dot de
2021-04-06 14:12 ` vries at gcc dot gnu.org
2021-04-06 14:29 ` vries at gcc dot gnu.org
2021-04-06 15:51 ` matz at suse dot de
2021-04-07  2:51 ` tromey at sourceware dot org
2021-04-08  8:57 ` vries at gcc dot gnu.org
2021-04-08  9:44 ` vries at gcc dot gnu.org
2021-04-08 12:48 ` vries at gcc dot gnu.org
2021-04-08 12:56 ` matz at suse dot de
2021-04-08 13:10 ` tromey at sourceware dot org
2021-04-12 13:38 ` vries at gcc dot gnu.org
2021-04-13 15:35 ` vries at gcc dot gnu.org
2021-04-21 19:54 ` cvs-commit at gcc dot gnu.org
2021-04-21 19:55 ` vries at gcc dot gnu.org

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-27681-4717-ZCMypQXC4y@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: 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).