Summary: | Segmentation fault on PUT request | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Krisztian VASAS <iron> |
Component: | mod_actions | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | RESOLVED LATER | ||
Severity: | normal | Keywords: | MassUpdate |
Priority: | P2 | ||
Version: | 2.2.17 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: |
put error strace output
put error gdb backtrace |
Description
Krisztian VASAS
2011-04-05 11:07:08 UTC
Created attachment 26855 [details]
put error strace output
This is the strace output, different process but the same error.
Created attachment 26856 [details]
put error gdb backtrace
This is the gdb bt output
Your gdb backtrace shows an orderly abort (and means you compiled with DEBUG defined but without symbolic information - strange). There should be a message about the failed assertion in your error log. Immediately preceding messages could also be relevant. (In reply to comment #3) > Your gdb backtrace shows an orderly abort (and means you compiled with DEBUG > defined but without symbolic information - strange). There should be a message > about the failed assertion in your error log. Immediately preceding messages > could also be relevant. Yes, you are right. I compiled with DEBUG, but that was also strange for me that the symbols were missing. And yes, i found the message in the errorlog, here it is: [Tue Apr 05 16:56:41 2011] [crit] [Tue Apr 05 16:56:41 2011] file http_filters.c, line 523, assertion "totalread >= 0" failed And i forgot to mention that the file i tried was the output of the "cal" command. If you need more information, just tell me Is there any news? If you need more info, just tell me what do i have to do for this. Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |