From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 40030 invoked by alias); 14 Aug 2016 22:36:44 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 39990 invoked by uid 89); 14 Aug 2016 22:36:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1439, 7111, phil, 7.11.1 X-HELO: mail-qt0-f180.google.com Received: from mail-qt0-f180.google.com (HELO mail-qt0-f180.google.com) (209.85.216.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 14 Aug 2016 22:36:40 +0000 Received: by mail-qt0-f180.google.com with SMTP id 52so15145864qtq.3 for ; Sun, 14 Aug 2016 15:36:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X8I5FgjdC190S+O9Br8jKTsv+1LSt/CpKT0EgvkTscA=; b=FFLpiSQE+2jUqier3uMHx/H7tO61mfXrfRBCK1VaqyPNS2HZ1Oj89z5OV49OexYcgR XF0A1Biaqha3zVmyKrZjh9G5vwc5W876DMCuMbs8lQoZ51A733Q+WJD2ufH46vsWhN05 lAsE2HQYy7PZu3fOFc/TmmQaQqlfGe36URhA2bY4dVV2ODpjFKaC08YGkHsR40wkyRdk NZTYvHrqRohkz0tyRPbdFwar2foh6hAFAdZKbCJHsPLzKBRh5LJHBlBjlwlI/KyYbZFT TJB72UumEhKgPPP6zMJVn9Aho+LJOJVEW/2EH5sB3qRKMRqUU1iOWvrNOYIHktID1b6p kRfA== X-Gm-Message-State: AEkoousTQOKDaxR2+5XF8R7VWB2VB4rJ3bFGdJGJDB/DeBpGBMFKqDb2vBbHedBchcejD7aHAGN5HogW43eYcA== X-Received: by 10.237.46.166 with SMTP id k35mr27974115qtd.93.1471214198542; Sun, 14 Aug 2016 15:36:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.27.148 with HTTP; Sun, 14 Aug 2016 15:36:08 -0700 (PDT) In-Reply-To: References: From: Philippe Proulx Date: Sun, 14 Aug 2016 22:36:00 -0000 Message-ID: Subject: Re: Process record does not support instruction 0xc5 at address... To: dwk Cc: gdb@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-08/txt/msg00027.txt.bz2 On Sun, Aug 14, 2016 at 5:42 PM, dwk wrote: > I used to run into this all the time with SIGSEGV, SIGINT, instruction > 0xcc, instruction 0xf4, etc. It seems to have been fixed when I upgraded > gdb at one point. I am currently using gdb 7.7.1 on x86-64. Your mileage > may vary. I'm on 7.11.1 by the way. Processor is Intel(R) Core(TM) i7-3520M with the following flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts Phil > > On Sun, Aug 14, 2016 at 5:30 PM, Philippe Proulx > wrote: >> Hello, >> >> Is there any known solution or workaround for this problem when >> using the GDB `record` command: >> >> Process record does not support instruction 0xc5 at address 0x7ffff7dee8a7. >> Process record: failed to record execution log. >> >> Program stopped. >> 0x00007ffff7dee8a7 in _dl_runtime_resolve_avx () from >> /lib64/ld-linux-x86-64.so.2 >> >> Thank you, >> >> Philippe Proulx