| View previous topic :: View next topic |
| Author |
Message |
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8011
Location: Salford, UK
|
 Posted: Wed Aug 21, 2024 7:28 am Post subject: |
 |
|
John
I don't experience the access violation when running your sample. So there appears to be some incompatiblity in the current download for v9.04. As you say, the access violation occurs when there is a runtime error and during the time when the traceback dialog is displayed.
1) I don't know how to redirect the output when running SDBG64.
2) ntdll.dll is a Microsoft system DLL. It is not scanned by SLINK64 and is presumably accessed from another Microsoft DLL such as user32.dll. |
|
| Back to top |
|
 |
JohnCampbell
Joined: 16 Feb 2006
Posts: 2580
Location: Sydney
|
| Posted: Wed Aug 21, 2024 7:45 am Post subject: |
|
|
| Quote: | | I don't experience the access violation when running your sample |
So you do not get the failure I am seeing ? That is a worry.
Could it be related to Win 10 and ntdll.dll ?
ntdll.dll is mentioned in the access violation failure trace back ?
It is now more of interest as "sdbg64 program" overcomes the error identifying problems when there is a program error, such as format data mismatch. |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8011
Location: Salford, UK
|
| Posted: Wed Aug 21, 2024 9:24 am Post subject: |
|
|
John
That's right. I can reproduce your experience but not the access violation.
I think that it is more likely to be a problem with SLINK64 and I am working on it. |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8011
Location: Salford, UK
|
| Posted: Wed Aug 21, 2024 2:31 pm Post subject: |
|
|
Work on this issue is on going.
As a work-around, when the traceback dialog fails to run, a shortened trace message can be diverted to the command line by setting the environment variable...
set SALFENVAR=kill_dialogbox |
|
| Back to top |
|
|
mecej4
Joined: 31 Oct 2006
Posts: 1896
|
| Posted: Wed Aug 21, 2024 6:35 pm Post subject: |
|
|
I have run into this problem (Slink64 3.10 reports access violation). If the output EXE file is named explicitly with the linker's /file:<name>.exe"option, the problem is not seen!
Last edited by mecej4 on Thu Aug 22, 2024 1:53 pm; edited 1 time in total |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8011
Location: Salford, UK
|
| Posted: Thu Aug 22, 2024 6:42 am Post subject: |
|
|
mecej4
Thank you for the feedback. It is useful to know this. |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 8011
Location: Salford, UK
|
| Posted: Tue Aug 27, 2024 1:20 pm Post subject: |
|
|
John
I have sent you a Personal Message (pm). |
|
| Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006
Posts: 2580
Location: Sydney
|
| Posted: Mon Sep 02, 2024 10:05 am Post subject: |
|
|
Hi Paul,
I tested the slink64 (ver 1.94 ? ) you provided, but it did not produce a noticeable difference when executing the program and reporting the access violation, rather than a trace back.
If I use "sdbg64 program.exe", this new executable stops at the format data mismatch with a useful error report.
Let me know if I can describe this in more detail
John |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
