Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print drmingw version in a crash report. #13

Closed
dismine opened this issue Jun 4, 2015 · 7 comments
Closed

Print drmingw version in a crash report. #13

dismine opened this issue Jun 4, 2015 · 7 comments

Comments

@dismine
Copy link

dismine commented Jun 4, 2015

What do you think about idea print in a crash report current drmingw version number? I think it will useful know which version generated report especially when we speak about debugging drmingw itself.

@renatosilva
Copy link

It would also be interesting to include version information for the application too, like implemented here.

@White-Tiger
Copy link

that's quite a good idea and simplifies bug reports from users (it's quite common that not every user is always using the latest version)

Though, does anyone know why "Daniel Atallah" used ZeroMemory in these 2 cases?

LPVOID pVer = malloc(size);
ZeroMemory(pVer, size);

OSVERSIONINFO osvi;
ZeroMemory(&osvi, sizeof(OSVERSIONINFO));
osvi.dwOSVersionInfoSize = sizeof(OSVERSIONINFO);

I guess this would be a cleaner way of doing it:

LPVOID pVer = calloc(size, 1);

OSVERSIONINFO osvi = {sizeof(OSVERSIONINFO)};

@jrfonseca
Copy link
Owner

It would also be interesting to include version information for the application too, like implemented here.

@renatosilva It seems a good enhancement. Could you please rebase the patch -- it would need to be re-applied to src/common/log.c -- and file a separate issue (maybe a pull request)?

@jrfonseca
Copy link
Owner

What do you think about idea print in a crash report current drmingw version number? I think it will useful know which version generated report especially when we speak about debugging drmingw itself.

@dismine I don't feel strongly either way (not sure if it would be useful or distracting.) Could you give an example of what you had in mind?

@dismine
Copy link
Author

dismine commented Jun 7, 2015

Could you give an example of what you had in mind?

Some time ago i tried debug my program because got many crash reports from users. Reason for these reports was false alarm crashes. After you fixed them (not all i think) i still get reports from old versions. But because i can't determine drmingw version i will spend more time trying understand is it fixed false alarm report or not. For me debugging my program it is also debugging drmingw.

Also have version number in crash report will cause less questions about used drmingw version in that case.

@jrfonseca
Copy link
Owner

@dismine, Right, I understand where you're coming from.

My question was more in practical terms: where should the version appear and how should be printed.

For example, would a

Report done written by ExcHndl X.Y.Z.

line at the end work, or should it be something less conspicuous like

DrMinGW X.Y.Z

(I don't actually use ExcHndl myself. Nowadays I only use DrMinGW itself.)

@dismine
Copy link
Author

dismine commented Jun 8, 2015

I like second

DrMinGW X.Y.Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants