Summary: | devel/dmalloc: dmallocth pthread loop | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | heas |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | arved, danfe, gerald, mjl, w.schwarzenfeld |
Priority: | --- | Keywords: | needs-qa |
Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(mjl) |
Hardware: | Any | ||
OS: | Any |
Description
heas
2016-02-05 00:51:41 UTC
I have never used dmallocth before, sorry. I can reproduce your crash on amd64. But if I add -dmalloc to the cc command (i used cc rather than gcc) then the program runs fine. Do you need to link against both? Have you contacted upstream about the bug? Hi. No, -ldmalloc is not required. I believe they provide all the same symbols, just one with locking and one without. And, if I add -ldmalloc after -ldmallocth, it still dumps core. And, no, I have not contacted the author. I do not know if it is a dmalloc bug or something related to the port (or fbsd). Have to start somewhere. :/ Is this still relevant, or could it be closed? (In reply to w.schwarzenfeld from comment #3) I was able to reproduce the bug. It is relevant but I don't understand enough about the internals of freebsd to fix. Added the maintainer of gcc. Maybe, he knows to solve. (In reply to mjl from comment #4) > I was able to reproduce the bug. Looks like you've recently submitted port update PR (bug #252124), is this particular problem fixed in the new version? Apologies for taking so long to reply. The update does not fix it. However, I did go and look at the docs: https://dmalloc.com/docs/dmalloc.html#Using-With-Threads I was able to have the conftest program in this report exit cleanly with -o 2. with -o 1, it core dumped. I believe the default is 0 (line 221 of env.c). I could look at adjusting the default but it could be the case that this introduces other problems. My recommendation is that this bug be closed. |