Joerg Schilling wrote:
Linda Walsh <suse@tlinx.org> wrote:
Joerg Schilling wrote:
I did never see any coredump from star and you did never report such a problem, I therefore assume that such problems do not exist.
That's fine, no coredumps were left in the CWD
Already mentioned running with one of suse's latest copies from factory -- at most a few months old. with version nums and dated april this year... So the fact that suse hasn't updated their copy in 5 years, and the fact that it dumps core -- in this case before it started, .. usually it gets at least a few run... maybe (in this case) the CWD didn't exist and that causes a problem too?
star: No such file or directory. Cannot change directory to '/backups/law/Documents/.'. Ishtar:law/bin> star*** buffer overflow detected ***: star terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x3001cfe607] /lib64/libc.so.6[0x3001cfc6e0] star[0x4278b5] star[0x4194cc] star[0x41a1b8] star[0x41a1b8]
Sorry, but if you cannot send at least a stacktrace with function names, I cannot help.
Why do you think I didn't send in a bug report. You've disabled coredumps but then expect the user to send tracebacks? It's hard enough to send in bug reports, and get shat on for not having a development system that is equivalent to a sterile build environment, but when programs turn off stack tracing but then require it for bug reports, it gets to be too much of a bother. It's too bad too, as I wouldn't have run into the error if I wasn't using it (had it running in a cron job for, at least, a few years, before it started failing -- likely anything above opensuse 11.3. Why would you, as a developer, turn off coredumps, but then require them for bug reporting. You said before, no one has reported these bugs that have been in the product for at least 3-4 years, maybe no one else wants to deal with the problems in generating things that you have disabled (unless suse did it for all products, but that would seem unbelievably irresponsible, so I may be erring on the side of naivety)... If you want to claim your program works reliably, not turning off coredumps and making sure large vendors like suse have your latest work and not a 5-yro copy would be great place to start.
Does this happen with a recent star?
Is there an alternate SuSE repo that has a newer one? AFAIK, the one in factory is the latest version. As mentioned, it's only 4 months old -- have you made any changes that would fix this in the past 4 months? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org