| Summary: | Gentoo Bug Reporting Guide is not sufficient | ||
|---|---|---|---|
| Product: | [OLD] Docs-user | Reporter: | Attila Stehr <as.gentoo> |
| Component: | Other | Assignee: | Docs Team <docs-team> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
not really ... your example is most likely from pretty bad memory corruption which no amount of CFLAGS will change Did you take a look on the link I gave? Did u take on the workaround of that bug? I bet Mr Petten Did you take a look on the link I gave? Did u take on the workaround of that bug? I bet Mr Pettenò didnt tell me to use those settings just for fun! yes, and it looks like Diego is responding to your comment #23/#24 where you never said you changed your CFLAGS, just your FEATURES/USE Thats not true! Please have a look on bug # 96073 comment #12 where Diego says > Can you try building it with debug information (CFLAGS="-g -ggdb3 -pipe" > FEATURES="nostrip" USE="debug") and try to get a backtrace for it? and I replied in bug # 96073 comment #12 with > okay, results: OF COURSE I kept those CFLAGS with the later testing! sorry I replied in comment # 13 By the way: bug # 96073 comment 27 gives my emerge --info which contains this line: CFLAGS="-march=athlon64 -O1 -pipe -fomit-frame-pointer -g -ggdb3" yes but your comment #13 didnt include anything useful the point is, the specific CFLAGS a developer uses are matter of habit ... what the bugzilla howto specifies is OK (In reply to comment #7) > yes but your comment #13 didnt include anything useful How can u say that? >:-| _MY_COMMENT_ contained the result of using Diegos instructions!!! That it did not alter sth on the problem does NOT mean its USELESS! The information it contains is: "setting those flags etc. does not help us to get closer to the problem". That is an information, RIGHT? Otherwise please tell me now that I shall NEVER reply on requests - like that of Diego - when the problem persists! > the point is, the specific CFLAGS a developer uses are matter of habit ... what > the bugzilla howto specifies is OK That may be. Nonetheless your comment above is quite arrogant. I rather like obliging people like Diego... i was refering to the gdb backtrace, not to your comment in general ... calm down the xine app caught the SIGTRAP signal and exited gracefully ... unless you through a break in there, gdb wont halt and thus it provided no useful information to further debug the issue (In reply to comment #9) > i was refering to the gdb backtrace, not to your comment in general ... calm down Okay then... seems I wasn't able to read that out of "your comment #13 didnt include anything useful". > the xine app caught the SIGTRAP signal and exited gracefully ... unless you > through a break in there, gdb wont halt and thus it provided no useful > information to further debug the issue So where does the bug reporting guide tell me to do that? |
The guide says --------------------------------------- | Code Listing 2.2: make.conf settings | | | CFLAGS="-O2 -pipe -ggdb3" | CXXFLAGS="${CFLAGS}" ---------------------------------------- When it should be CFLAGS "-g -ggdb3 -O1" Reproducible: Always Steps to Reproduce: See https://bugs.gentoo.org/show_bug.cgi?id=96073#c25 as well.