Date: Tue, 10 Jul 2018 04:56:35 +0800 From: "Peter Zhang" <proudtek@edm.proudtek.com> To: freebsd-dtrace@freebsd.org Subject: Access Control Card - MIFARE 1K NXP S50 EPOXY Card Message-ID: <S7Y1.p9ra2zxv8jWxNDQ2NLsf46toSUAA03@edm.proudtek.com>
index | next in thread | raw e-mail
click here for the webversion (http://edm.proudtek.com/x/?S7Y1.p9ra2zxP8fW0PJ.ka2JoaGxpRkAA47) MIFARE 1K Epoxy Card New Generation MIFARE 1k Access Control Card In access control, in public traffic, in hotel key system, and various membership system, ....... We have been using the credit card size RFID card for many years, and are used to it already. But if you have ever seen our new generation exquisite RFID Epoxy Card. You might want to throw your old card away immediately, because of the following features: Crystal Looking - luxury appearance Clearn Surface - it is dust-proof and oil proff, Personalized Shape - more than 100 molds for choice, plus developping customized molds. Eyelet - easy to hang with metal rings or elastic rope Small Size - can be kept in pocket or bag conveniently, Durable - there is extra layer of epoxy protecting the inner PVC cards. Water Proof - The epoxy and PVC material is resistant to water We are a professional RFID component supplier since 2008, producing top quality RFID cards, RFID keyfobs, and RFID wristbands wtih most kinds of chips: EM4200, EM4305, ATA5577, MIFARE 1K, MIFARE Ultralight, MIFARE DESFire, Jcop, etc. We have strict quality control system, all product has been tested 3 to 4 times during production and 100% inspected before delivery. Millions of our RFID compents to Germany, Sweden, USA, Australia, etc. each year, Most of our customers cooperate with us for long term, and place orders to us repeatedly. If you are still hesitating, write back to us for free sample, and see it by yourself! If you are impressed by our description, write back to us for free sample, and lift your access control business to a new high level! ------------- Kind Regards Peter Zhang | Business Development Manager Shenzhen Proud Tek Co.,LTD. A208, Zhantao Scienc & Technology Mansion, Minzhi Ave, Longhua District, Shenzhen, China Tel: +86-755 23765843 | Mob: +86-18665820632 Email: 77418523@qq.com (mailto:peter@proudtek.com) | Skype: zhnepi click here to unsubscribe (http://edm.proudtek.com/x/plugin/?pName=unsubscribe&MIDRID=S7Y1.p9ra2zxP8fW0PJ.ka2JoaGxpRkAA47&Z=-1610362836) From owner-freebsd-dtrace@freebsd.org Fri Jul 13 17:54:21 2018 Return-Path: <owner-freebsd-dtrace@freebsd.org> Delivered-To: freebsd-dtrace@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6A351046329 for <freebsd-dtrace@mailman.ysv.freebsd.org>; Fri, 13 Jul 2018 17:54:20 +0000 (UTC) (envelope-from ashfixit@gmail.com) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F471713A1 for <freebsd-dtrace@freebsd.org>; Fri, 13 Jul 2018 17:54:20 +0000 (UTC) (envelope-from ashfixit@gmail.com) Received: by mail-yw0-x230.google.com with SMTP id w76-v6so12035171ywg.4 for <freebsd-dtrace@freebsd.org>; Fri, 13 Jul 2018 10:54:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s 161025; h=mime-version:from:date:message-id:subject:to; bhPmdLkChnKs+QbEL2JMGB9VQdtnYzCZpZwHW1O/L0A=; bJICRkMI6O5ot11jOiSN7C329JzzJK8JMnbEGEh24/qDws+4ly3Oy0lbrmjDDca/T kRssaW80LNeUrbUiq4RzLiZ163tLc123w8LQXQG1ull4/xHjb32hqXgyXbnj35NeNwNW Mxk7IfW3mz46ds3wKtM6K/xISchTPQA8JiOPfyoWdKtCeKMyeYAVZgEO8gNkFK9hx5Ev bh8W7z0+TCezFi7f9icXF4BjIN+zaAecfKe1+j2y1RqeIa5+N5nEVMQ6oei8QcFAnXPA k0V95PQu3ecCHHF+8dOIlQsdFODpoqrgv/QsgAC0mTxNaZVhYDSxvXJ/7OTeV3HZtPbX ucpg=X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d100.net; s 161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bhPmdLkChnKs+QbEL2JMGB9VQdtnYzCZpZwHW1O/L0A=; b=EHJmVIaRBPSew4Nb0/PH42cycqKUY8nNyN7yxMtgwC2e1QDW0tybZgyvkDJVyhrxwU bC2yDh9Fmpq2Stds8vKevuO6W70UTTbFZCYyiWw4311WUVy6QnivsPAHCX+acjLDk918 16Nhxo8n6AqQisucjyj+d+rERhpSeGz8qn3maOXefdTsAm0twW0XOPF9Gy2dThOjhRcj hJzugUbaXJXjM8CE33zkvXLZN1m7fGGempcsIGnCcnEtAJ/b2sKSx2WxRFWyf0mNELC6 fxfgMupXvfzGMn3C2Ia/nns+25X1TFcOxt+hQlK2DdjryJRg7I3BkmICSLSdv8u6Dl2T grWw=X-Gm-Message-State: AOUpUlGgerBiJgvlJXH9W+QE/yA3zrLPIJeR+C/nCjUNJ24pqCn6Ocrl kLM3zjvxpZWF1ylXhyX7oGQ/je3F4Y5qOdfFGtQX-Google-Smtp-Source: AAOMgpeVH7R2x1I98TN/Ny+mOzpm3LSaQE4EddBqLH5wAnf0WGtyx7zI8DDHuGGgYnvhEKOcMnwYRJ4QUwI+4k7nQIUX-Received: by 2002:a81:3e02:: with SMTP id l2-v6mr4006191ywa.381.1531504459303; Fri, 13 Jul 2018 10:54:19 -0700 (PDT) MIME-Version: 1.0 From: Ash Gokhale <ashfixit@gmail.com> Date: Fri, 13 Jul 2018 13:54:05 -0400 Message-ID: <CAHpe+0Y158uwwPR6wbZmp+E1_uKBABBBnY3n3j-S-imyxmiUqg@mail.gmail.com> Subject: dtrace compiler crash compiling additional identical predicates. To: freebsd-dtrace@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." <freebsd-dtrace.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-dtrace>, <mailto:freebsd-dtrace-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-dtrace/> List-Post: <mailto:freebsd-dtrace@freebsd.org> List-Help: <mailto:freebsd-dtrace-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace>, <mailto:freebsd-dtrace-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 13 Jul 2018 17:54:21 -0000 While developing a long dtrace script; I seem to be tripping over a compiler bug. I can tickle the bug by using this in a predicate / self->thing_var != "" / one too many times. Although I use that exact construction many times. Changing the probe , or even providing an invalid probe does not change the crash. Commenting out the predicate saves the compile. Comparing self->var to an integer compiles ok, ( while not really making sense in the context). The compiler will segv when asked to produce the IR via 'dtrace -S -ls srcipt.dt' Efforts to reproduce the crash with a reduced dtrace file have been futile and the system is sufficiently custom that sharing the script may not be useful. Has anyone else seen this crash? Has anyone noticed arbitrary size limit on dtrace scripts? [New LWP 103111] Core was generated by `dtrace -v -s drive-lifecycle.dt'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000800cf5910 in strchr () from /lib/libc.so.7 Thread 1 (LWP 103111): #0 0x0000000800cf5910 in strchr () from /lib/libc.so.7 #1 0x000000080090999f in ctf_lookup_by_name (fp=<optimized out>, name=<optimized out>) at /usr/src/cddl/contrib/opensolaris/common/ctf/ctf_lookup.c:138 #2 0x00000008006b8716 in dtrace_lookup_by_type (dtp=0x801644000, object=<optimized out>, name=0x803bc8010 "str", tip=<optimized out>) at /usr/src/cddl/contrib /opensolaris/lib/libdtrace/common/dt_module.c:1639 #3 0x000000080069c0ce in id_or_type (s=0x803bc8010 "str") at /usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_lex.l:775 #4 0x00000008006ade05 in yyparse () at dt_grammar.c:1388 #5 0x00000008006a973f in dt_compile (dtp=<optimized out>, context63, pspec=DTRACE_PROBESPEC_NAME, arg=0x0, cflags=0, argc=1, argv=0x80064c000, fp=<optimized out>, s=0x0) at /usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_cc.c:2457 #6 0x00000008006aaf90 in dtrace_program_fcompile (dtp=0x803bc8fff, fp=0x803bc8010, cflags4, argc=-2139062144, argv=0x3) at /usr/src/cddl/contrib/opensolari s/lib/libdtrace/common/dt_cc.c:2594 #7 0x000000000040493f in compile_file (dcp=0x801638180) at /usr/src/cddl/contrib/opensolaris/cmd/dtrace/dtrace.c:805 #8 0x000000000040311e in main (argc=4, argv=<optimized out>) at /usr/src/cddl/contrib/opensolaris/cmd/dtrace/dtrace.c:1725help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?S7Y1.p9ra2zxv8jWxNDQ2NLsf46toSUAA03>
