Comments (4)
1. Computer name and IP address is personally identifiable information. I do not
think someone will want to provide such information. Can you give an example of
why
you may need such info?
Even if we implement such feature, we need to warn user and request his consent
before sending report.
2. The number of CPUs is already implemented as standard feature.
3. Amount of RAM installed as well as how much memory the process was using at
the
time of crash - OK, this is not personal info, we can easily add this.
4. "Would be very useful to know the type of video card installed as well as the
driver version of that video card." I do not think many developers will use such
feature, but we can implement this as option. User consent is required to send
such
info.
5. "total amount of disk space that and free disk space". This may be useful,
but
what if there are several disks? User consent is required on this.
Original comment by [email protected]
on 22 Nov 2009 at 11:57
- Changed state: Accepted
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from crashrpt.
In my case I want to identify the person that sent the crash report. The
reports are
less useful without knowing from which company the report came from.
My companies use of an automated report system is perhaps different than
others. My
company provides the hardware to end-users that our software runs on. These
systems
do not belong to any individual end-users. The PCs are company workstations that
perform data processing.
I understand that CrashRpt is used by other companies or individuals where
personal
information could be a problem, but in my case personal information is not an
issue.
My end-users do not use the systems as personal workstations.
As far as user consent goes, there are times where no one will be around to
consent.
For example, a server style process is running and crashes. The desired
behavior is
that a crash report is automatically sent and the process is restarted (I
requested
auto process restart upon crash in another request) - User consent is not
possible
here yet we will still need screenshots as well as the PC name.
My experience has been with bugtrap. It requires user consent only if the
programmer
requests it. It is possible to configure bugtrap in such a way that it does not
ask
for any consent. Sometimes this is necessary.
Original comment by [email protected]
on 23 Nov 2009 at 3:27
from crashrpt.
I'm thinking about your need of user's identification. You would like to
identify
users by IP or by NetBIOS computer name, while other developers may need other
ways
of identification (e.g., by license key or by user name). We can't add all these
identification mechainsms in CrashRpt.
So, I would offer to implement some extension mechanism for CrashRpt XML file.
We can
introduce crAddProperty(lpszPropId, lpszPropValue); function that would allow
developer to collect some custom info on crash and add it to XML (for example
to add
user IP). On the side of crprober.exe, this property can be extracted from ZIP
file
by using crpGetProperty() function.
What do you think?
Original comment by [email protected]
on 3 Dec 2009 at 5:39
from crashrpt.
Original comment by [email protected]
on 23 Dec 2009 at 7:09
- Changed state: Fixed
from crashrpt.
Related Issues (20)
- Remove VS2005/ATL Compatibility HOT 2
- CrashRpt is not capturing Exact exception information some times. its crashed at crashHandler HOT 1
- Crashrpt not able to handle the Exceptions from ActiveX Controller call back in MFC . HOT 2
- can't make the crashreporter installed HOT 2
- No minidump created sometimes - reports "Only part of a ReadProcessMemory or WriteProcessMemory request was completed" HOT 1
- [deleted issue]
- Capture only windows belonging to the process HOT 1
- Czech localization HOT 2
- Potential crash in CrashSender.exe HOT 1
- uiAccess=true elevated process cannot create minidump HOT 1
- not compilable under Visual Studio 2013 HOT 5
- Include Polish translation (attached) HOT 1
- Redirects to a different server are not handled HOT 1
- If the crashsender is redirected, the crash report upload may happen twice.
- CrashCallback not working in VS 2013 HOT 3
- CrashSender crashes with access violation
- Can't make CrashRpt work with Qt HOT 1
- Translation files
- Setting bContinueExecution generates report twice
- can't open the crashfix server website HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from crashrpt.