summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* New upstream release (v3.10.14)v3.10.14David Sommerseth2013-04-051-1/+1
| | | | Signed-off-by: David Sommerseth <davids@redhat.com>
* Do not add explictly 'dmispec' attributes inside switch() in dmi_decode()David Sommerseth2013-04-051-2/+0
| | | | | | | | | | The dmispec attribute is added outside the switch() call, and must not be duplicated. If this happens, an invalid XML file will be generated. (Un)fortunately, libxml2 is quite forgiving to this error. But xmllint will complain about it and other XML libraries (such as python-lxml) may reject such XML data. Signed-off-by: David Sommerseth <davids@redhat.com>
* Harden dmi_string() calls with better NULL checksDavid Sommerseth2011-01-063-10/+28
| | | | | | | | This patch fixes more potential issues where dmi_string() results was not necessarily checked for NULL, which potentially could lead to SEGV issues. Signed-off-by: David Sommerseth <davids@redhat.com>
* Make use of dmixml_AddDMIstring() where possibleDavid Sommerseth2011-01-061-65/+68
| | | | | | | | This modifies the core DMI decoding to make use of the new dmixml_AddDMIstring() function instead of the older, more error prone approach of dmi_string() and dmixml_AddTextChild(). Signed-off-by: David Sommerseth <davids@redhat.com>
* Implemented dmixml_AddDMIstring()David Sommerseth2011-01-062-0/+43
| | | | | | | | | This function can be used instead of dmi_string() and dmixml_AddTextChild(). In those cases where dmi_string() returns NULL, this situation is handled more gracefully. In addition of also handling "not specified" situations better as well. Signed-off-by: David Sommerseth <davids@redhat.com>
* Add SIGILL catcher in mem_chunk()David Sommerseth2010-10-271-14/+53
| | | | | | | | | | | | On some s390x systems under heavy memory load seems to trigger a SIGILL event when calling memcpy(). To avoid this issue, which basically leads to the complete script to core dump, a signal handler was implemented to add tackle such siutations more gracefully. The SIGILL event should now be logged as well, to be able to see that this happened. Signed-off-by: David Sommerseth <dazo@users.sourceforge.net>
* New upstream release - v3.10.13Nima Talebi2010-06-031-1/+1
|
* Fixed an issue causing SEGV on some hardware when dmi_processor_id() is calledDavid Sommerseth2010-05-261-2/+1
| | | | | The dmi_processor_id() function did not check the char *version pointer if it was NULL before doing strcmp(). On some hardware, *version will be NULL.
* v3.10.12 in light of recent bugfix releaseNima Talebi2010-03-121-1/+1
| | | | Also, switch to dpkg-source 3.0 (quilt) format.
* Allow format strings to be NULL in dmixml_Add*() functionsDavid Sommerseth2010-04-201-5/+19
| | | | | | | | | | | This bug was reported by Jan Hutař <jhutar@redhat.com> [1] The implemented fix avoids assertions if the format strings to dmixml_AddAttribute(), dmixml_AddTextChild() and dmixml_AddTextContent() functions are NULL. In these cases, it will result in an empty value instead of returning NULL from these functions. [1] <https://bugzilla.redhat.com/show_bug.cgi?id=583867>
* Add a little hint where decoding got abortedDavid Sommerseth2010-04-201-2/+2
|
* New feature release (log handling)v3.10.11Nima Talebi2010-02-161-1/+1
|
* New upstream release (v3.10.10)Nima Talebi2010-02-161-1/+1
|
* Improved DMIerror message tag when decoding is not possibleDavid Sommerseth2010-02-051-6/+16
| | | | Plus some minor code style clean up
* Removed not needed \n from log_append() entriesDavid Sommerseth2010-02-056-14/+14
|
* Added logging flag to log_append() to change log behaviourDavid Sommerseth2010-02-058-65/+83
| | | | | | | | | | | | | | Valid flags are: * LOGFL_NORMAL Log all messages to the log context, and send log message to stderr on errors * LOGFL_NODUPS Log only unique messages. Duplicated messages will be removed * LOGFL_NOSTDERR Don't write to stderr, even if errors occur
* Ported fprintf() -> log_append() on XML functionsDavid Sommerseth2010-01-085-63/+74
|
* Update Python build rulesDavid Sommerseth2010-01-082-0/+2
|
* Port dmidump to use the new log APIDavid Sommerseth2010-01-081-4/+4
| | | | | | This port will not create a new log buffer (Log_t), but log_append() will print errors to stderr in this case, as the log buffer pointer is NULL.
* More fprintf() -> log_append() portingDavid Sommerseth2010-01-087-34/+36
|
* Implement a global log buffer and start porting fprint() -> log_append()David Sommerseth2010-01-082-24/+75
|
* Don't print false error warning if logp == NULLDavid Sommerseth2010-01-081-1/+7
|
* Added a new log APIDavid Sommerseth2010-01-082-0/+266
|
* Moved write_dump() over to dmidump.c, as this is the only user of this functionDavid Sommerseth2010-01-082-36/+38
|
* Removed struct dmi_minor. It was not used anywhere.David Sommerseth2010-01-081-8/+0
|
* Make sure const char *filename is not a wild pointerDavid Sommerseth2010-01-071-1/+1
|
* Removed not needed informationDavid Sommerseth2010-01-071-1/+0
|
* Forgot to update versioning informationv3.10.9Nima Talebi2010-01-071-1/+1
| | | | | (Despite dazo automating the process with a script, it was obviously still too difficult).
* Changes necessary to keep Debian packages saneNima Talebi2010-01-061-1/+1
| | | | | | | | Both setup.py and setup-dbg.py install the same file, namely: /usr/share/pyshared/dmidecode.py This generated Bug#561904. This commit closes this bug.
* Improved set_dev() functionDavid Sommerseth2009-12-171-5/+17
| | | | | | | | | This function would often fail during the unit test. Most probably because the complete error checking was a bit odd. Rewritten the error checks to be a bit more sane. Also improved error situations, where it will now throw an exception with an error message instead of just returning False.
* Take endinanness into consideration when compilingDavid Sommerseth2009-12-143-2/+14
|
* Spelling fixesNima Talebi2009-12-142-2/+2
| | | | Thanks Lintian! You're a champ!
* Changed version number to 3.10.8David Sommerseth2009-12-101-1/+1
|
* New release (3.10.7)Nima Talebi2009-09-231-1/+1
|
* Moved a OS-specific library settings out to commonv3.10.6-rc1Nima Talebi2009-08-033-6/+8
| | | | | The libxml2 path is now handled by `setup_common.py', so the actual setup files are clean from any OS-specific (Debian/RedHat) hacks.
* Completed python XML map for TypeMap 0x26David Sommerseth2009-07-021-2/+18
|
* Completed python XML map for TypeMap 0x21David Sommerseth2009-07-021-1/+17
|
* Completed python XML map for TypeMap 0x1EDavid Sommerseth2009-07-021-1/+13
|
* Completed python XML map for TypeMap 0x1CDavid Sommerseth2009-07-022-2/+25
|
* Completed python XML map for TypeMap 0x1BDavid Sommerseth2009-07-021-1/+11
|
* Completed python XML map for TypeMap 0x1ADavid Sommerseth2009-07-021-1/+24
|
* Completed python XML map for TypeMap 0x19David Sommerseth2009-07-021-1/+9
| | | | | | | | | | Format has changed slightly. The original format in v2.10 was: {'Next Scheduled Power-on': [' *','-*',' 0',':0',':0']} The new format is: {'Next Scheduled Power-on': '*-* *:*:*'} The reason is that the formatting in the original list was rather half-done, containing separators in some of the elements.
* Completed python XML map for TypeMap 0x18David Sommerseth2009-07-021-1/+16
|
* Completed python XML map for TypeMap 0x17David Sommerseth2009-07-021-1/+17
|
* Completed python XML map for TypeMap 0x16David Sommerseth2009-07-022-2/+23
|
* Completed python XML map for TypeMap 0x15David Sommerseth2009-07-021-0/+10
|
* Completed python XML map for TypeMap 0x14David Sommerseth2009-07-021-1/+18
|
* Completed python XML map for TypeMap 0x13David Sommerseth2009-07-021-1/+14
|
* Completed python XML map for TypeMap 0x12David Sommerseth2009-07-021-1/+18
|
* Completed python XML map for TypeMap 0x0CDavid Sommerseth2009-07-021-1/+11
|
generated by cgit (git 2.34.1) at 2025-12-31 09:50:33 +0000