A null pointer bug in linux - docker

Recently, we met a kernel panic issue due to NULL pointer dereference in
the function ixgbevf_alloc_rx_buffers when up or down the VF into docker container. We
can reproduce the issue when up down vf in container.
Driver and kernel information:
driver: ixgbe
version: 4.4.0-k-rh7.3
driver: ixgbevf
version: 2.12.1-k-rh7.3
host kernel: centos
Linux 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
BUG:
[15332.577915] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
[15332.578277] IP: [<ffffffffa05dc610>] ixgbevf_alloc_rx_buffers+0x60/0x180 [ixgbevf]
[15332.578569] PGD 3ed27a0067 PUD 3ed27a3067 PMD 0
[15332.579034] Oops: 0000 [#1] SMP
[15332.579512] Modules linked in: ixgbevf xt_set ip_set_hash_ipportnet ip_set_bitmap_port ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xt_conntrack br_netfilter bridge stp llc overlay(T) iptable_filter xt_addrtype iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack intel_powerclamp coretemp intel_rapl iosf_mbi kvm_intel kvm irqbypass crc32_pclmul iTCO_wdt ghash_clmulni_intel aesni_intel iTCO_vendor_support mxm_wmi lrw gf128mul glue_helper ablk_helper cryptd mei_me ipmi_devintf pcspkr mei sg i2c_i801 lpc_ich ipmi_si ipmi_msghandler wmi shpchp acpi_power_meter ip_tables xfs libcrc32c sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul ast crct10dif_common
[15332.583611] crc32c_intel drm_kms_helper syscopyarea sysfillrect sysimgblt ixgbe fb_sys_fops ttm igb mdio ahci drm ptp libahci pps_core dca i2c_algo_bit libata megaraid_sas i2c_core fjes dm_mirror dm_region_hash dm_log dm_mod
[15332.586109] CPU: 30 PID: 302 Comm: kworker/u80:1 Tainted: G ------------ T 3.10.0-514.26.2.el7.x86_64 #1
[15332.587224] Hardware name: Sugon I610-G20/60G24-US, BIOS 006 08/07/2017
[15332.588322] Workqueue: ixgbevf ixgbevf_service_task [ixgbevf]
[15332.589099] task: ffff881ffd121f60 ti: ffff881ffd134000 task.ti: ffff881ffd134000
[15332.589912] RIP: 0010:[<ffffffffa05dc610>] [<ffffffffa05dc610>] ixgbevf_alloc_rx_buffers+0x60/0x180 [ixgbevf]
[15332.590770] RSP: 0018:ffff881ffd137d20 EFLAGS: 00010287
[15332.591638] RAX: 0000000000000200 RBX: 0000000000000000 RCX: 0000000000000000
[15332.592534] RDX: 0000000000000000 RSI: 00000000000001ff RDI: ffff883fe13eaf00
[15332.593438] RBP: ffff881ffd137d58 R08: ffff881ffd134000 R09: 0000000000000000
[15332.594361] R10: 0000000000000001 R11: 0000000000000005 R12: 0000000000000000
[15332.595300] R13: 00000000fffffe00 R14: 00000000000001ff R15: ffff883fe13eaf00
[15332.596248] FS: 0000000000000000(0000) GS:ffff883fff280000(0000) knlGS:0000000000000000
[15332.597224] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[15332.598231] CR2: 0000000000000008 CR3: 0000003ef3b68000 CR4: 00000000003407e0
[15332.599257] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[15332.600281] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[15332.601325] Stack:
[15332.602352] ffff883f85ab3ba8 ffff881ffd137d38 ffff883f85ab38c0 0000000000000009
[15332.603431] ffff883f85ab3ba8 ffff883fe13eaf00 0000000000001028 ffff881ffd137db8
[15332.604526] ffffffffa05de7af 0000003e00000000 ffff883f85ab38c0 0000000000001028
[15332.605641] Call Trace:
[15332.606757] [<ffffffffa05de7af>] ixgbevf_configure+0x5af/0x720 [ixgbevf]
[15332.608078] [<ffffffffa05e04b5>] ixgbevf_reinit_locked+0x65/0x90 [ixgbevf]
[15332.609329] [<ffffffffa05e172f>] ixgbevf_service_task+0x29f/0x370 [ixgbevf]
[15332.610515] [<ffffffff810a845b>] process_one_work+0x17b/0x470
[15332.611710] [<ffffffff810a9296>] worker_thread+0x126/0x410
[15332.612916] [<ffffffff810a9170>] ? rescuer_thread+0x460/0x460
[15332.614136] [<ffffffff810b0a4f>] kthread+0xcf/0xe0
[15332.615371] [<ffffffff810b0980>] ? kthread_create_on_node+0x140/0x140
[15332.616618] [<ffffffff81697758>] ret_from_fork+0x58/0x90
[15332.617877] [<ffffffff810b0980>] ? kthread_create_on_node+0x140/0x140
[15332.619153] Code: c5 41 89 f6 49 89 c4 48 8d 14 40 48 8b 47 38 49 c1 e4 04 4c 03 67 18 48 8d 1c d0 0f b7 47 2c 41 29 c5 66 0f 1f 84 00 00 00 00 00 <48> 83 7b 08 00 74 76 8b 53 10 48 8b 03 48 01 d0 49 83 c4 10 48
[15332.621915] RIP [<ffffffffa05dc610>] ixgbevf_alloc_rx_buffers+0x60/0x180 [ixgbevf]
[15332.623301] RSP <ffff881ffd137d20>
[15332.624659] CR2: 0000000000000008
Does somebody have get this bug before?And how to fix it?

we update lxbge resolve this problem:
pci:Intel Corporation Ethernet Controller 10-Gigabit X540-AT2
lxbge version: 5.3.7
kernel version: 4.4.138-1.el7.elrepo.x86_64
linux release: Release: 7.4.1708

Related

How to get to know TCP or UDP protocol from wireshark pcap hexadecimal view

A sample TCP hexadecimal Wireshark capture shown below,
0000 6c 6a 77 8d 48 cf 96 38 a7 7d 02 de 08 00 45 28
0010 00 34 56 92 40 00 28 06 fa e9 a2 7d 13 09 c0 a8
0020 8a f1 01 bb df 84 20 00 27 8e e3 6f a9 7f 80 10
0030 00 7c 25 f3 00 00 01 01 08 0a 54 48 f8 cc 61 38
0040 eb 22
How to get to know TCP or UDP protocol from Wireshark pcap hexadecimal view ?.
Save the hex data, as shown, into a text file and then run text2pcap file.txt file.pcap. You can then load the file.pcap file into Wireshark. Run text2pcap -h for more help or refer to the text2pcap man page for more details about that tool.
0000 6c 6a 77 8d 48 cf 96 38 a7 7d 02 de 08 00 45 28
0010 00 34 56 92 40 00 28 06 fa e9 a2 7d 13 09 c0 a8
8th Byte in the second line we have to check. In here it's 06. So protocol number 06 is TCP. Like wise we can get to know the protocol number from hexadecimal view.

Raspberry Pi 3 can't connect to iOS' Personal Hotspot

I'm currently working on an iOS app which needs to pair to a custom external device (smart camera relying on a Raspberry Pi 3) to work correctly. The pairing mechanism is currently based on WebSockets, so the app and the camera needs to be on the same network to be discovered and work correctly.
For now, when both the app and the smart camera are on the same WiFi network, the pairing works, and everything work as expected. Nonetheless, the app needs to work even if it is not connected to an external WiFi network. So we thought we could use the iOS' Personal Hotspot to connect the smart camera to, so as to enable the pairing (since it would then be on the same network).
But, we're currently encountering a problem, after enabling Personal Hotspot from iOS, the camera either :
does not "see" the WiFi Network, so it can't connect to it
when the network is visible, it does not connect to the Personal Hotspot : it
keeps trying to negotiate keys, and authenticating without success
When this problem occurs, we also tried to connect a Windows 7 laptop and a MacBookPro (running latest Sierra), but the WiFi connexion to iOS' Personal Hotspot could not been established either, with similar behaviors (wifi visibility, impossible to authenticate, connexion stabiliy...). So the problem does not seem to come with some network configuration on external devices, but more on the Personal Hotspot feature.
The logs on iOS are not very clear to me, so if someone could give a little insight it would be great:
par défaut 17:54:18.918592 +0200 sharingd Updated tethering support result = YES, wifiResult = YES, netRBResult = YES, firstUnlocked = YES
par défaut 17:54:18.918789 +0200 sharingd state = 1023, reason = 0
par défaut 17:54:18.918958 +0200 sharingd connected hosts = 1, only usb = NO, flipped switch on = NO, wifiClient = <WiFiManagerClient 0x101d2e630 [0x1b3994240]>, discovery state = YES, hostAPNetwork = YES, network timer = (null)
erreur 17:54:18.919786 +0200 locationd WifiMgr, error, bssid invalid, <private>, #CloneMe
erreur 17:54:18.920172 +0200 locationd WifiMgr, error, bssid invalid, <private>, #CloneMe
par défaut 17:54:18.920834 +0200 CommCenter #I Calling _CTGetCellularDataIsEnabled()
par défaut 17:54:18.929647 +0200 analyticsd [<private>] no observers; dropped.
par défaut 17:54:18.932031 +0200 symptomsd SCDynamicStore config_callback: k: com.apple.MobileInternetSharing
par défaut 17:54:18.932686 +0200 symptomsd SCDynamicStore key: com.apple.MobileInternetSharing, interfaces: {}
par défaut 17:54:18.947974 +0200 hostapd STA d4:7b:b0:8:37:a associated
par défaut 17:54:18.951673 +0200 hostapd STA d4:7b:b0:08:37:0a event 1 notification
par défaut 17:54:18.957204 +0200 hostapd STA d4:7b:b0:08:37:0a start authentication
par défaut 17:54:18.959079 +0200 hostapd STA d4:7b:b0:8:37:a DEAUTHORIZED.
par défaut 17:54:18.961158 +0200 hostapd STA d4:7b:b0:08:37:0a sending 1/4 msg of 4-Way Handshake
par défaut 17:54:19.044584 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 C9 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 BF EF 92 FF 9E FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:19.242918 +0200 hostapd STA d4:7b:b0:08:37:0a received EAPOL-Key frame (2/4 Pairwise)
par défaut 17:54:19.245172 +0200 hostapd STA d4:7b:b0:08:37:0a MIC OK
par défaut 17:54:19.248415 +0200 hostapd STA d4:7b:b0:08:37:0a sending 3/4 msg of 4-Way Handshake
par défaut 17:54:19.799258 +0200 CommCenter QMI: Svc=0xe2(BSP) Req MsgId=0xe002 Bin=[<private>]
par défaut 17:54:19.840969 +0200 CommCenter QMI: Svc=0xe2(BSP) Resp MsgId=0xe002 Bin=[<private>]
par défaut 17:54:20.049299 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 CA 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 BB EE 94 FF 7C FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:21.042898 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 CB 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 B8 EC 94 FF B6 FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:21.806955 +0200 CommCenter QMI: Svc=0xe2(BSP) Req MsgId=0xe002 Bin=[<private>]
par défaut 17:54:21.847338 +0200 CommCenter QMI: Svc=0xe2(BSP) Resp MsgId=0xe002 Bin=[<private>]
par défaut 17:54:22.041651 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 CC 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 B7 EC 96 FF C0 FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:23.048387 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 CD 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 B4 ED 94 FF DA FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:23.816292 +0200 CommCenter QMI: Svc=0xe2(BSP) Req MsgId=0xe002 Bin=[<private>]
par défaut 17:54:23.867039 +0200 CommCenter QMI: Svc=0xe2(BSP) Resp MsgId=0xe002 Bin=[<private>]
par défaut 17:54:24.048262 +0200 CommCenter QMI: Svc=0x03(NAS) Ind MsgId=0x0051 Bin=['01 2A 00 80 03 05 04 CE 39 51 00 1E 00 11 08 00 83 05 00 00 96 FF FF FF 14 06 00 BC EF 93 FF 86 FF A2 01 00 32 A4 03 00 01 32 00']
par défaut 17:54:24.935783 +0200 CommCenter #I Data usage threshold reached for tethering, bytes consumed: 110254 total consumed:: 730740
par défaut 17:54:24.940706 +0200 CommCenter #I Cumulative bytes at threshold: 61045158, Previous value: 59016742, Delta: 2028416
par défaut 17:54:24.942240 +0200 CommCenter Threshold reached when entity: (uuid: <private> euuid: <private> pid: 4120 epid: 4120 process: <private> bundle id: <private>) consumed: (889770 bytes) on source: (identifier: 0x101f64630)
par défaut 17:54:24.942995 +0200 CommCenter #I Data usage threshold reached for internet context
We've tried to test the Personal Hotspot on several iOS devices (iPhones 5, 5S, 6, 6+, 6S, SE, 7, 7+ both running latest iOS 10 version), and with no explanation, it only worked when the iPhone SE shared its connexion (?!?)...
We're quite stuck on this, since iOS does not give much settings/information on Personal Hotspot, and it is a user-level feature, with no API to control it.
What we've come to with some WiFi tools, it seems that iOS uses WPA2 Personal algorithm for securing its Personal Hotspot, but any additional information might be useful for us...
For the moment, we have already tried :
Rename iPhone to remove any space and/or special characters
Use a very simple password with no spaces and/or special characters
Encode WiFi name in a base64 string on the Raspberry 3 /etc/wpa_supplicant/wpa_supplicant.conf conforming to this post but with no success
My wpa_supplicant.conf file looks currently like this :
network = {
ssid=aVBob25lNg0K
psk="passphrase"
key_mgmt=WPA-PSK
}
When pairing fails on a Raspberry Pi 3, the following logs can be observed :
Trying to associate with 76:8d:08:74:3c:33 (SSID='iphone6' freq=2412 MHz)
CTRL-EVENT-ASSOC-REJECT status_code=16
CTRL-EVENT-SCAN-STARTED
CTRL-EVENT-SCAN-RESULT
Do you have an idea of what could mean CTRL-EVENT-ASSOC-REJECT status_code=16
Any help or similar problem/experience from others people will be much appreciated, because this feature is critical for us, and a core to our business. For information, when the hotpot is hosted by an Android phone, everything works fine.
Thanks in advance for your help,

Connect to Windows SQL Server 2008 R2 from Rails app

My Rails 4.2.1 app has to connect to a Microsoft SQL 2008 R2 database. I am using the tiny_tds gem version 1.0.4. FreeTDS v1.00.15 is installed on the production server running Ubuntu 14.04.
I run queries inside an each loop and I can't get the loop to complete, the process crashes before completion.
I tried playing with tiny_tds options without success.
Here's the code I am using to get the tiny_tds client (check tds_version and timeout options):
client = TinyTds::Client.new(username: db_conf['username'], password: db_conf['password'], host: db_conf['host'], port: db_conf['port'], database: db_conf['database'], tds_version: '7.3', timeout: 15000, appname: 'ERP')
Here's the FreeTDS log after such an error happens.
packet.c:741:Sending packet 0000 12 01 00 ce 00 00 00 00-16 03 01 00
86 10 00 00 |........ ........| 0010 82 00 80 6e d9 e2 dc 97-9d 77 59
9a 5b da e3 e2 |...n.... .wY.[...| 0020 8b aa 66 ed ec 5e e2 02-e5 6c
fd db e1 ef 47 1a |..f..^.. .l....G.| 0030 9d 63 03 ed 6d 3e 28 3b-b9
64 fd 92 71 34 ff ba |.c..m>(; .d..q4..| 0040 7d 3c 8d ee 7b 34 75
e9-d5 b7 c6 83 a9 7d e6 7f |}<..{4u. .....}..| 0050 71 7e 25 11 82 b8
76 b1-c6 ba 86 b4 c3 0a 47 f0 |q~%...v. ......G.| 0060 51 96 c7 e2 5f
ca 07 b2-95 53 b9 9e bb 2c e7 cb |Q..._... .S...,..| 0070 be 0a b5 eb
b0 f3 41 1d-cd 86 fc a6 53 08 5e 56 |......A. ....S.^V| 0080 29 85 79
14 dc 2b 74 7b-b2 43 2c e8 0e 87 60 e4 |).y..+t{ .C,....| 0090 10 ef
f8 14 03 01 00 01-01 16 03 01 00 30 c7 f0 |........ .....0..| 00a0 35
f5 2c 6e 79 8d 85 b9-bd 60 b7 09 8c 7e 29 18 |5.,ny... ....~).| 00b0
4a 56 ea c3 4e 13 bf e3-c5 8d f6 68 31 31 54 ee |JV..N... ...h11T.|
00c0 bf 2f 75 8d e9 9e c0 a9-d0 d2 9e 5b c9 92 |./u..... ...[..|
tls.c:105:in tds_pull_func_login query.c:3796:tds_disconnect()
util.c:165:Changed query state from IDLE to DEAD
util.c:322:tdserror(0x80b75e0, 0xa04ca80, 20017, 0)
dblib.c:7947:dbperror(0xae62780, 20017, 0) dblib.c:8015:dbperror:
Calling dblib_err_handler with msgno = 20017; msg->msgtext =
"Unexpected EOF from the server (192.168.32.105:1433)"
dblib.c:5777:dbgetuserdata(0xae62780) dblib.c:8037:dbperror:
dblib_err_handler for msgno = 20017; msg->msgtext = "Unexpected EOF
from the server (192.168.32.105:1433)" -- returns 2 (INT_CANCEL)
util.c:352:tdserror: client library returned TDS_INT_CANCEL(2)
util.c:375:tdserror: returning TDS_INT_CANCEL(2) util.c:375:tdserror:
returning TDS_INT_CANCEL(2) tls.c:942:handshake failed
login.c:530:login packet rejected util.c:322:tdserror(0x80b75e0,
0xa04ca80, 20002, 0) dblib.c:7947:dbperror(0xae62780, 20002, 0)
dblib.c:8015:dbperror: Calling dblib_err_handler with msgno = 20002;
msg->msgtext = "Adaptive Server connection failed"
And here's the output of tsql -C:
~$ tsql -C
Compile-time settings (established with the "configure" script)
Version: freetds v1.00.15
freetds.conf directory: /usr/local/etc
MS db-lib source compatibility: no
Sybase binary compatibility: no
Thread safety: yes
iconv library: yes
TDS version: auto
iODBC: no
unixodbc: no
SSPI "trusted" logins: no
Kerberos: no
OpenSSL: yes
GnuTLS: no
MARS: no
Any idea what I should do to fix those Unexpected EOF from the server errors?
In your FreeTDS configuration (often in /etc/freetds/freetds.conf as in your configuration), change the value of text size:
text size = 4294967295
That's the maximum value, IIRC. I believe with FreeTDS 0.91 that your default is probably 64512.
Looking at the SQL Profiler, I found out the Rails application was opening way too many connections on the MSSQL server. Upon reaching its max number of open connection, the MSSQL server refused opening any new connection, resulting in the Unexpected EOF from the server error.
To solve the issue, I had to reuse my open connection when sending queries instead of opening a new connection for each query. I guess this is the correct way to use the tiny_tds connector anyway.
Translated to code:
def self.get_pmi_client
if ##pmi_client.nil? or !##pmi_client.active?
db_conf = Rails.configuration.database_configuration["pmi_#{Rails.env}"]
##pmi_client = TinyTds::Client.new(username: db_conf['username'], password: db_conf['password'], host: db_conf['host'], port: db_conf['port'], database: db_conf['database'])
raise MSSQLConnectionError, t('erp.errors.pmi_connection_error') unless ##pmi_client.active?
end
return ##pmi_client
end

Apple push notification not working for distribution/ad hoc testing

I have been using sandbox push notification for a while, and it is working perfectly. After switching to distribution, push notification stopped working.
Things that I have checked:
Two separate push notification certificates are created, one for development (Sandbox) and one for distribution(production).
Device token is different for sandbox and production.
We use NotNoop APNS on server side. The certificate.p12 is created by exporting the private key under push notification certificate in Apple Keychain Access. Certificate itself is not in the p12 file.
Checked archived package for production with command
codesign -d --entitlements :- "Payload/YourApp.app"
And the code signing entitlement is distribution.
Followed Apple TN 2265 (https://developer.apple.com/library/ios/technotes/tn2265/_index.html). While using openssl to connect to APNS, the connection is closed right after handshake (for production). For sandbox, there is a pause after the handshake, and then more reads & writes.
My command:
> openssl pkcs12 -in Cert_prod.p12 -out Cert_prod.pem
> openssl s_client -connect gateway.push.apple.com:2195 -cert Cert_prod.pem -debug -showcerts -CAfile "Entrust.pem"
The output (for production):
...
Server certificate
subject=/C=US/ST=California/L=Cupertino/O=Apple Inc./CN=gateway.push.apple.com
issuer=/C=US/O=Entrust, Inc./OU=www.entrust.net/rpa is incorporated by reference/OU=(c) 2009 Entrust, Inc./CN=Entrust Certification Authority - L1C
---
Acceptable client certificate CA names
/C=US/O=Apple Inc./OU=Apple Certification Authority/CN=Apple Root CA
/C=US/O=Apple Inc./OU=Apple Worldwide Developer Relations/CN=Apple Worldwide Developer Relations Certification Authority
/C=US/O=Apple Inc./OU=Apple Certification Authority/CN=Apple Application Integration Certification Authority
---
SSL handshake has read 3144 bytes and written 2161 bytes
---
New, TLSv1/SSLv3, Cipher is AES256-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : AES256-SHA
Session-ID:
Session-ID-ctx:
Master-Key: CCCE22D7487589D257E547F2693E8AEDF86B693E6EFE09DCAA7EE74C28812E45506A21B0DC0ED6CAAF4395EB2D2899ED
Key-Arg : None
Start Time: 1454828210
Timeout : 300 (sec)
Verify return code: 0 (ok)
---
read from 0x7fa6d3a00060 [0x7fa6d4806600] (5 bytes => 5 (0x5))
0000 - 15 03 01 ...
0005 - <SPACES/NULS>
read from 0x7fa6d3a00060 [0x7fa6d4806605] (32 bytes => 32 (0x20))
0000 - 8f c6 74 25 a6 40 2b 58-29 bc a4 e0 a7 c9 43 a8 ..t%.#+X).....C.
0010 - a0 93 62 78 6a 73 ed aa-4f 61 0a a4 9e fe a7 9e ..bxjs..Oa......
closed
write to 0x7fa6d3a00060 [0x7fa6d480b000] (37 bytes => 37 (0x25))
0000 - 15 03 01 00 20 2c 70 db-af 76 7a 2c 01 70 da 0f .... ,p..vz,.p..
0010 - a9 03 da e2 fb 69 f8 09-63 5d 18 85 81 8c 31 63 .....i..c]....1c
0020 - 63 fb 73 cb 48 c.s.H
The output (for sandbox):
...
Server certificate
subject=/C=US/ST=California/L=Cupertino/O=Apple Inc./CN=gateway.sandbox.push.apple.com
issuer=/C=US/O=Entrust, Inc./OU=www.entrust.net/rpa is incorporated by reference/OU=(c) 2009 Entrust, Inc./CN=Entrust Certification Authority - L1C
---
Acceptable client certificate CA names
/C=US/O=Apple Inc./OU=Apple Certification Authority/CN=Apple Root CA
/C=US/O=Apple Inc./OU=Apple Worldwide Developer Relations/CN=Apple Worldwide Developer Relations Certification Authority
/C=US/O=Apple Inc./OU=Apple Certification Authority/CN=Apple Application Integration Certification Authority
---
SSL handshake has read 3160 bytes and written 2161 bytes
---
New, TLSv1/SSLv3, Cipher is AES256-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : AES256-SHA
Session-ID:
Session-ID-ctx:
Master-Key: 011B90857BC02D4A9DCB7300F8C9F368905F90EA4BDDC0677CD2EA9AAB3550CF750F0B57C5AF0C72F5BCD991658AC4AC
Key-Arg : None
Start Time: 1454828396
Timeout : 300 (sec)
Verify return code: 0 (ok)
---
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (74 bytes => 74 (0x4A))
0000 - 17 03 01 00 20 d7 a1 a1-b2 9e be ce 49 18 26 0e .... .......I.&.
0010 - 46 73 f9 dc 7f b2 75 71-f6 bf 51 65 44 0e f1 60 Fs....uq..QeD..`
0020 - fe 80 2e e2 a6 17 03 01-00 20 f0 be dc 70 85 b0 ......... ...p..
0030 - 82 d0 44 1e 9a b8 fe 59-39 b1 14 be 0a 9d 7c 0e ..D....Y9.....|.
0040 - ce 09 9b c3 f2 1c dd 28-c7 24 .......(.$
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (74 bytes => 74 (0x4A))
0000 - 17 03 01 00 20 4c 12 4f-f9 ba 0b e4 80 b3 66 bb .... L.O......f.
0010 - 93 a7 c9 47 9d 84 36 88-33 c0 80 79 a2 97 c6 95 ...G..6.3..y....
0020 - 2a 4b 42 c1 bc 17 03 01-00 20 a0 4d 06 fd 84 78 *KB...... .M...x
0030 - 3d b9 12 ad 65 75 b6 1a-01 91 28 86 40 c4 e9 c2 =...eu....(.#...
0040 - 38 91 47 42 c3 1d e3 c7-f9 41 8.GB.....A
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (74 bytes => 74 (0x4A))
0000 - 17 03 01 00 20 35 77 28-ea b0 80 5a ad 9e 99 87 .... 5w(...Z....
0010 - 7d 07 13 14 ff ea a8 48-60 7c 46 f0 59 07 c8 53 }......H`|F.Y..S
0020 - 3f 96 55 fc ec 17 03 01-00 20 60 49 00 86 bf 41 ?.U...... `I...A
0030 - 70 70 5c d5 d7 f5 83 4c-8a b3 10 22 bb ad 4c f2 pp\....L..."..L.
0040 - 3e e0 54 db 5d e7 2e bc-cc 9c >.T.].....
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (74 bytes => 74 (0x4A))
0000 - 17 03 01 00 20 25 d3 8a-20 a4 4c 3c b6 f7 fe 95 .... %.. .L<....
0010 - 60 e2 5b 9f fc fd 3d e7-4c 27 cc d0 8e 6c ef 30 `.[...=.L'...l.0
0020 - 56 4a 88 a9 f9 17 03 01-00 20 cc 32 2d d5 e6 ff VJ....... .2-...
0030 - 59 26 14 67 2d 3f 3d 88-d3 3b ea 53 5e 11 72 75 Y&.g-?=..;.S^.ru
0040 - a4 c6 0e d8 95 b4 21 e3-5d dd ......!.].
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (74 bytes => 74 (0x4A))
0000 - 17 03 01 00 20 8a a0 b6-fd 72 7b f4 f6 ef de 65 .... ....r{....e
0010 - 76 40 6b 67 1d b8 83 c1-92 98 50 9e 0f ac d7 da v#kg......P.....
0020 - 66 39 9c 39 9f 17 03 01-00 20 70 a4 1d 63 f1 6e f9.9..... p..c.n
0030 - d6 5a b3 fd f9 7e de de-64 7d 42 0d da 94 59 09 .Z...~..d}B...Y.
0040 - 93 3f 33 e3 d7 d0 3e 2e-10 e7 .?3...>...
read from 0x7f9b19c1aef0 [0x7f9b1a014600] (5 bytes => 5 (0x5))
0000 - 15 03 01 ...
0005 - <SPACES/NULS>
read from 0x7f9b19c1aef0 [0x7f9b1a014605] (32 bytes => 32 (0x20))
0000 - 60 b6 57 1c 8a 8e e9 f0-59 b5 27 73 f5 ba de b1 `.W.....Y.'s....
0010 - 7a ef d7 ab 79 23 0a ea-b2 13 c9 ca 98 e5 c3 36 z...y#.........6
closed
write to 0x7f9b19c1aef0 [0x7f9b1a019000] (37 bytes => 37 (0x25))
0000 - 15 03 01 00 20 f2 6f d0-1b 8d 41 5e 44 df f5 49 .... .o...A^D..I
0010 - 3a 09 6a 11 2b 3b f3 47-1e 70 8d 8d a8 9d 42 45 :.j.+;.G.p....BE
0020 - e9 47 18 26 3e .G.&>
Therefore, it seems that the broken link is between my server and APNS. How can I know why the connection is closed?
I suspected that something is wrong on the certificate, but could not find anything. I took the same steps to create sandbox certificates, and they worked just fine. Did I miss anything for production?
Other related links that I checked:
apple push notification not working in production
http://www.raywenderlich.com/32960/apple-push-notification-services-in-ios-6-tutorial-part-1
Couldn't able to connect to APNS Sandbox server
The certificate.p12 in NotNoop APNS should be exported from the certificate only, without the private key. In Keychain Access, click the small arrow next to the push notification certificate to show the private key, select the certificate only (without the key), and export it to a .p12 file. Updating the file on server solved my problem. Openssl is a good tool for smoke test before archiving the app and running it in ad hoc mode.

Access violation registering Canvas classes

I have been getting a few bug reports for an access violation that occurs while registering Canvas classes at startup, more specifically performing an #IntfClear during TCustomDX10Context.CheckDevice.
Full bugreport:
date/time : 2014-06-04, 18:05:43, 594ms
computer name : <...>
user name : <...>
registered owner : <...>
operating system : Windows 7 x64 Service Pack 1 build 7601
system language : English
system up time : 54 minutes 48 seconds
program up time : 99 milliseconds
processors : 4x Intel(R) Core(TM) i5 CPU 661 # 3.33GHz
physical memory : 5055/8055 MB (free/total)
free disk space : (C:) 91.84 GB
display mode : 1920x1080, 32 bit
process id : $18c0
allocated memory : 71.76 MB
executable : <...>.exe
exec. date/time : 2014-05-29 22:36
version : 3.2.1.2
compiled with : Delphi XE3
madExcept version : 4.0.6
callstack crc : $077d2d6c, $53160fd9, $53160fd9
exception number : 1
exception class : EAccessViolation
exception message : Zugriffsverletzung bei Adresse 077D2D6C. Lesen von Adresse 000000AE.
main thread ($d0):
077d2d6c +000 ???
0040e028 +010 <...>.exe System 191 +0 #IntfClear
0096af25 +0cd <...>.exe FMX.Context.DX10 TCustomDX10Context.CheckDevice
00976559 +005 <...>.exe FMX.Canvas.D2D RegisterCanvasClasses
00990c6c +000 <...>.exe FMX.Platform.Win 3404 +0 TPlatformWin.RegisterCanvasClasses
009d6312 +056 <...>.exe FMX.Types TCanvasManager.GetDefaultCanvas
009d62aa +00e <...>.exe FMX.Types TCanvasManager.CreateFromWindow
00a0574e +026 <...>.exe FMX.Forms TCustomForm.CreateHandle
009fff91 +0b9 <...>.exe FMX.Forms TCommonCustomForm.InitializeNewForm
00a054fa +006 <...>.exe FMX.Forms TCustomForm.InitializeNewForm
009ffce4 +094 <...>.exe FMX.Forms TCommonCustomForm.Create
00a056c6 +016 <...>.exe FMX.Forms TCustomForm.Create
009fb947 +057 <...>.exe FMX.Forms TApplication.CreateForm
009fbb0b +05f <...>.exe FMX.Forms TApplication.RealCreateForms
00988861 +011 <...>.exe FMX.Platform.Win 461 +1 TPlatformWin.Run
009fe821 +0d1 <...>.exe FMX.Forms TApplication.Run
00beccf4 +2c0 <...>.exe <...> 106 +39 initialization
75863388 +010 kernel32.dll BaseThreadInitThunk
thread $186c:
778a0156 +0e ntdll.dll NtWaitForMultipleObjects
76e715f1 +fa KERNELBASE.dll WaitForMultipleObjectsEx
758619f3 +89 kernel32.dll WaitForMultipleObjectsEx
75330864 +00 USER32.dll MsgWaitForMultipleObjectsEx
75330b64 +1a USER32.dll MsgWaitForMultipleObjects
004a42e9 +0d <...>.exe madExcept CallThreadProcSafe
004a434e +32 <...>.exe madExcept ThreadExceptFrame
75863388 +10 kernel32.dll BaseThreadInitThunk
>> created by main thread ($d0) at:
734878e1 +00 gdiplus.dll
thread $1288: <priority:1>
7789f8ca +0e ntdll.dll NtWaitForSingleObject
76e714a5 +92 KERNELBASE.dll WaitForSingleObjectEx
7586118f +3e kernel32.dll WaitForSingleObjectEx
75861143 +0d kernel32.dll WaitForSingleObject
004a42e9 +0d <...>.exe madExcept CallThreadProcSafe
004a434e +32 <...>.exe madExcept ThreadExceptFrame
75863388 +10 kernel32.dll BaseThreadInitThunk
>> created by main thread ($d0) at:
54377390 +00 nvwgf2um.dll
thread $28c:
778a1f3f +0b ntdll.dll NtWaitForWorkViaWorkerFactory
75863388 +10 kernel32.dll BaseThreadInitThunk
thread $1bcc:
778a1f3f +0b ntdll.dll NtWaitForWorkViaWorkerFactory
75863388 +10 kernel32.dll BaseThreadInitThunk
modules:
00400000 <...>.exe 3.2.1.2 C:\<...>
10000000 nvspcap.dll 10.11.15.0 C:\Windows\system32
53c10000 nvwgf2um.dll 9.18.13.2723 C:\Windows\system32
603d0000 AcGenral.DLL 6.1.7601.18128 C:\Windows\AppPatch
606d0000 atkdx11disp.dll 7.14.10.305 C:\Windows\system32
60700000 d3d10_1core.dll 6.2.9200.16492 C:\Windows\system32
60750000 d3d10_1.dll 6.2.9200.16492 C:\Windows\system32
60780000 security.dll 6.1.7600.16385 C:\Windows\system32
60790000 FaultRep.dll 6.1.7601.17514 C:\Windows\system32
607f0000 sfc_os.DLL 6.1.7600.16385 C:\Windows\system32
60800000 sfc.dll 6.1.7600.16385 C:\Windows\system32
6ed00000 d3d11.dll 6.2.9200.16570 C:\Windows\system32
706d0000 dxgi.dll 6.2.9200.16492 C:\Windows\system32
70ca0000 propsys.dll 7.0.7601.17514 C:\Windows\system32
70e00000 d3d9.dll 6.1.7601.17514 C:\Windows\system32
70fd0000 nvapi.dll 9.18.13.2723 C:\Windows\system32
71a50000 comctl32.dll 6.10.7601.17514 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2
71bf0000 winmm.dll 6.1.7601.17514 C:\Windows\system32
72150000 samcli.dll 6.1.7601.17514 C:\Windows\system32
73210000 MSACM32.dll 6.1.7600.16385 C:\Windows\system32
73230000 d3d8thk.dll 6.1.7600.16385 C:\Windows\system32
73440000 gdiplus.dll 6.1.7601.18120 C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36
73890000 apphelp.dll 6.1.7601.17514 C:\Windows\system32
738e0000 MPR.dll 6.1.7600.16385 C:\Windows\system32
73ca0000 wsock32.dll 6.1.7600.16385 C:\Windows\system32
73f20000 SECUR32.DLL 6.1.7601.18443 C:\Windows\system32
74090000 dwmapi.dll 6.1.7600.16385 C:\Windows\system32
74100000 UxTheme.dll 6.1.7600.16385 C:\Windows\system32
742e0000 comctl32.dll 5.82.7601.18201 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5
74f90000 profapi.dll 6.1.7600.16385 C:\Windows\system32
74fa0000 USERENV.dll 6.1.7601.17514 C:\Windows\system32
750b0000 ntmarta.dll 6.1.7600.16385 C:\Windows\system32
750e0000 sophos_detoured.dll 10.3.3.128 C:\Program Files (x86)\Sophos\Sophos Anti-Virus
75130000 winspool.drv 6.1.7601.17514 C:\Windows\system32
75190000 version.dll 6.1.7600.16385 C:\Windows\system32
752a0000 CRYPTBASE.dll 6.1.7600.16385 C:\Windows\syswow64
752b0000 SspiCli.dll 6.1.7601.18443 C:\Windows\syswow64
75310000 USER32.dll 6.1.7601.17514 C:\Windows\syswow64
75410000 iertutil.dll 11.0.9600.17041 C:\Windows\syswow64
75630000 SETUPAPI.dll 6.1.7601.17514 C:\Windows\syswow64
757d0000 PSAPI.DLL 6.1.7600.16385 C:\Windows\syswow64
757e0000 api-ms-win-downlevel-normaliz-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
757f0000 NSI.dll 6.1.7600.16385 C:\Windows\syswow64
75800000 WLDAP32.dll 6.1.7601.17514 C:\Windows\syswow64
75850000 kernel32.dll 6.1.7601.18409 C:\Windows\syswow64
759f0000 DEVOBJ.dll 6.1.7601.17621 C:\Windows\syswow64
75a10000 RPCRT4.dll 6.1.7601.18205 C:\Windows\syswow64
75b00000 WININET.dll 11.0.9600.17041 C:\Windows\syswow64
75cc0000 shell32.dll 6.1.7601.18429 C:\Windows\syswow64
76910000 WS2_32.dll 6.1.7601.17514 C:\Windows\syswow64
769b0000 api-ms-win-downlevel-advapi32-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
769c0000 MSCTF.dll 6.1.7600.16385 C:\Windows\syswow64
76a90000 comdlg32.dll 6.1.7601.17514 C:\Windows\syswow64
76b10000 api-ms-win-downlevel-shlwapi-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
76b50000 msvcrt.dll 7.0.7601.17744 C:\Windows\syswow64
76c00000 api-ms-win-downlevel-ole32-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
76c10000 ole32.dll 6.1.7601.17514 C:\Windows\syswow64
76d70000 normaliz.DLL 6.1.7600.16385 C:\Windows\syswow64
76d80000 CLBCatQ.DLL 2001.12.8530.16385 C:\Windows\syswow64
76e10000 CFGMGR32.dll 6.1.7601.17621 C:\Windows\syswow64
76e40000 sechost.dll 6.1.7600.16385 C:\Windows\SysWOW64
76e60000 KERNELBASE.dll 6.1.7601.18409 C:\Windows\syswow64
76eb0000 IMM32.DLL 6.1.7601.17514 C:\Windows\system32
76f10000 USP10.dll 1.626.7601.18009 C:\Windows\syswow64
76fb0000 WINTRUST.dll 6.1.7601.18205 C:\Windows\syswow64
76fe0000 api-ms-win-downlevel-version-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
76ff0000 CRYPT32.dll 6.1.7601.18277 C:\Windows\syswow64
77110000 MSASN1.dll 6.1.7601.17514 C:\Windows\syswow64
77120000 ADVAPI32.dll 6.1.7601.18247 C:\Windows\syswow64
771c0000 oleaut32.dll 6.1.7601.17676 C:\Windows\syswow64
77250000 SHLWAPI.dll 6.1.7601.17514 C:\Windows\syswow64
772b0000 api-ms-win-downlevel-user32-l1-1-0.dll 6.2.9200.16492 C:\Windows\syswow64
772c0000 GDI32.dll 6.1.7601.18275 C:\Windows\syswow64
77350000 urlmon.dll 11.0.9600.17041 C:\Windows\syswow64
77850000 LPK.dll 6.1.7601.18177 C:\Windows\syswow64
77880000 ntdll.dll 6.1.7601.18247 C:\Windows\SysWOW64
processes:
0000 Idle 0 0 0
0004 System 0 0 0
0120 smss.exe 0 0 0
01c8 csrss.exe 0 0 0
0210 wininit.exe 0 0 0
0224 csrss.exe 1 0 0
0250 services.exe 0 0 0
0260 lsass.exe 0 0 0
0268 lsm.exe 0 0 0
02d4 winlogon.exe 1 0 0
02f4 svchost.exe 0 0 0
0330 ATKFUSService.exe 0 0 0
0344 nvvsvc.exe 0 0 0
0360 nvSCPAPISvr.exe 0 0 0
038c svchost.exe 0 0 0
03c8 atiesrxx.exe 0 0 0
03f8 svchost.exe 0 0 0
014c svchost.exe 0 0 0
0298 svchost.exe 0 0 0
0228 svchost.exe 0 0 0
0454 audiodg.exe 0 0 0
04ac SavService.exe 0 0 0
04b8 atieclxx.exe 1 0 0
04c8 nvxdsync.exe 1 0 0
04d0 nvvsvc.exe 1 0 0
0614 ATKFastUserSwitching.exe 1 18 11 normal
0660 dwm.exe 1 18 2 high
0678 explorer.exe 1 356 266 normal
0790 svchost.exe 0 0 0
07e4 svchost.exe 0 0 0
0490 spoolsv.exe 0 0 0
082c taskhost.exe 1 25 23 normal
08d0 NvTmru.exe 1 9 4 normal C:\Program Files (x86)\NVIDIA Corporation\NVIDIA Update Core
0924 NvBackend.exe 1 9 4 normal C:\Program Files (x86)\NVIDIA Corporation\Update Core
0944 ANIWConnService.exe 0 0 0
0980 ANIWZCSdS.exe 0 0 0
099c RtlService.exe 0 0 0
09dc flux.exe 1 22 13 normal C:\Users\<...>\AppData\Local\FluxSoftware\Flux
09f4 SpotifyWebHelper.exe 1 9 3 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
0a3c nvtray.exe 1 81 5 normal
0a74 BCUService.exe 0 0 0
0aac FABS.exe 0 0 0
0ae0 RtWLan.exe 1 0 0
0b48 NvNetworkService.exe 0 0 0
0ba8 nvstreamsvc.exe 0 0 0
0610 spotify.exe 1 222 81 normal C:\Users\<...>\AppData\Roaming\Spotify
046c razerhid.exe 1 9 5 normal C:\Program Files (x86)\Razer\Arctosa
09c8 BCU.exe 1 9 4 normal C:\Program Files (x86)\DeviceVM\Browser Configuration Utility
0b9c jusched.exe 1 9 2 normal C:\Program Files (x86)\Common Files\Java\Java Update
0b84 PnkBstrA.exe 0 0 0
0910 PnkBstrB.exe 0 0 0
0920 SAVAdminService.exe 0 0 0
09d4 ALsvc.exe 0 0 0
0c70 swc_service.exe 0 0 0
0c98 svchost.exe 0 0 0
0cac swi_service.exe 0 0 0
0cec TurboBoost.exe 0 0 0
0d30 ALMon.exe 1 47 40 normal C:\Program Files (x86)\Sophos\AutoUpdate
0d60 WLIDSVC.EXE 0 0 0
0e04 WLIDSVCM.EXE 0 0 0
0efc WmiPrvSE.exe 0 0 0
0ff0 SearchIndexer.exe 0 0 0
0af0 svchost.exe 0 0 0
11b8 nvstreamsvc.exe 1 0 0
11cc conhost.exe 1 0 0
127c wmpnetwk.exe 0 0 0
130c svchost.exe 0 0 0
11d0 svchost.exe 0 0 0
1304 SpotifyHelper.exe 1 52 1 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
1134 SpotifyHelper.exe 1 33 1 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
15c8 SpotifyHelper.exe 1 13 3 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
17a8 dllhost.exe 0 0 0
151c LMS.exe 0 0 0
14b0 svchost.exe 0 0 0
1018 UNS.exe 0 0 0
059c SpotifyHelper.exe 1 142 1 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
08d8 SpotifyHelper.exe 1 11 1 normal C:\Users\<...>\AppData\Roaming\Spotify\Data
0abc chrome.exe 1 375 53 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
0eb4 chrome.exe 1 12 5 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
12d8 chrome.exe 1 11 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
0da8 chrome.exe 1 719 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
10bc chrome.exe 1 11 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
1114 chrome.exe 1 9 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
0968 chrome.exe 1 11 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
1220 chrome.exe 1 10 1 normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
1974 jucheck.exe 1 12 6 normal C:\Program Files (x86)\Common Files\Java\Java Update
0778 chrome.exe 1 251 1 below normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
1144 WINWORD.EXE 1 474 118 normal C:\Program Files (x86)\Microsoft Office\Office14
0cc4 OSPPSVC.EXE 0 0 0
17b8 splwow64.exe 1 4 2 normal
1410 SearchProtocolHost.exe 0 0 0
1258 SearchFilterHost.exe 0 0 0 idle
18e0 chrome.exe 1 209 1 below normal C:\Users\<...>\AppData\Local\Google\Chrome\Application
18c0 <...>.exe 1 36 34 normal C:\<...>
cpu registers:
eax = 00000000
ebx = 00000000
ecx = 00000000
edx = 00000008
esi = 0018fca4
edi = 077d2d6c
eip = 077d2d6c
esp = 0018fc60
ebp = 077d2444
stack dump:
0018fc60 a4 fc 18 00 44 24 7d 07 - 6c 2d 7d 07 44 24 00 06 ....D$}.l-}.D$..
0018fc70 2c 63 de 6e 48 81 7d 07 - 6c 2d 7d 07 00 00 00 00 ,c.nH.}.l-}.....
0018fc80 01 00 00 00 00 00 00 00 - ac fc 18 00 42 00 d2 6e ............B..n
0018fc90 6c 2d 7d 07 01 00 00 00 - 58 25 7d 07 44 24 7d 07 l-}.....X%}.D$}.
0018fca0 3c 27 7d 07 3c 27 7d 07 - 3c a6 d0 6e c0 fc 18 00 <'}.<'}.<..n....
0018fcb0 1b ff d1 6e 6c 2d 7d 07 - 44 24 7d 07 a0 00 00 00 ...nl-}.D$}.....
0018fcc0 cc fc 18 00 43 25 d1 6e - 3c 27 7d 07 e0 fc 18 00 ....C%.n<'}.....
0018fcd0 6d 6d d1 6e fc 26 7d 07 - 00 00 00 00 3c 24 7d 07 mm.n.&}.....<$}.
0018fce0 ec fc 18 00 f1 26 d1 6e - 10 24 7d 07 f8 fc 18 00 .....&.n.$}.....
0018fcf0 52 c1 d4 6e 3c 24 7d 07 - 14 fd 18 00 5f 39 d1 6e R..n<$}....._9.n
0018fd00 10 24 7d 07 04 34 d1 6e - 10 24 7d 07 66 38 d1 6e .$}..4.n.$}.f8.n
0018fd10 10 24 7d 07 28 fd 18 00 - 5f 34 d1 6e 00 00 00 00 .$}.(..._4.n....
0018fd20 16 00 00 00 90 05 00 00 - 34 fd 18 00 c5 25 d1 6e ........4....%.n
0018fd30 10 24 7d 07 40 fd 18 00 - d1 f5 d4 6e 3c 27 7d 07 .$}.#......n<'}.
0018fd40 84 fd 18 00 2b e0 40 00 - 74 27 7d 07 80 fd 18 00 ....+.#.t'}.....
0018fd50 2a af 96 00 60 fd 18 00 - 9c 98 40 00 84 fd 18 00 *...`.....#.....
0018fd60 6c fd 18 00 9c 98 40 00 - 84 fd 18 00 94 fd 18 00 l.....#.........
0018fd70 9c 98 40 00 84 fd 18 00 - a0 00 00 00 00 00 75 60 ..#...........u`
0018fd80 00 00 00 00 bc fd 18 00 - 5e 65 97 00 71 0c 99 00 ........^e..q...
0018fd90 15 63 9d 00 10 fe 18 00 - 9c 98 40 00 bc fd 18 00 .c........#.....
disassembling:
[...]
0040e01c jz loc_40e02c
0040e01e mov dword ptr [eax], 0
0040e024 push eax
0040e025 push edx
0040e026 mov eax, [edx]
0040e028 > call dword ptr [eax+8]
0040e02b pop eax
0040e02c ret
This is by no means happening on all machines but seems to be a very rare issue.
EDIT:
Following the suggestion of #Graymatter I've been able to establish an SSCCE.
program SSCCE;
{$APPTYPE CONSOLE}
{$R *.res}
uses System.SysUtils, FMX.Context.DX10;
begin
try
TCustomDX10Context.CheckDevice;
WriteLn('Everything went fine, guess we have to dig deeper.');
except
on E: Exception do Writeln(E.ClassName, ': ', E.Message);
end;
Write('Press enter to exit.');
ReadLn;
end.
The output produced is Zugriffsverletzung bei Adresse 05C1006C. Lesen von Adresse 06F29ED3 Any suggestions as to what to do about that ?

Resources