152065 – net-im/jabberd-2.0.11-r1 USE="debug" too aggressive

Bug 152065 - net-im/jabberd-2.0.11-r1 USE="debug" too aggressive

Summary: net-im/jabberd-2.0.11-r1 USE="debug" too aggressive

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	Krzysztof Pawlik (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	150107
	Show dependency tree

Reported:	2006-10-20 01:53 UTC by Alastair Tse (RETIRED)
Modified:	2006-10-21 04:43 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alastair Tse (RETIRED) gentoo-dev

2006-10-20 01:53:13 UTC

Jabberd 2.0.11-r1 is great, however, the USE="debug" behaviour has changed
so that instead of adding --enable-debug to the configure parameters, it
adds the other two extremely verbose memory debug flags which makes the
debug output nearly unusable.

Can we please restore it to the old behavour in 2.0.11? Thanks.

Comment 1 Krzysztof Pawlik (RETIRED) gentoo-dev

2006-10-20 02:22:44 UTC

It can be controlled by another USE flag, I'm open for suggestions what flag could it be? Adding two new flags: nad_debug and pool_debug or one memory_debug (or memdebug)? I'm for memdebug.

Comment 2 Krzysztof Pawlik (RETIRED) gentoo-dev

2006-10-21 04:43:03 UTC

"memdebug" added to jabberd-2.0.11-r1:

  21 Oct 2006; Krzysiek Pawlik <nelchael@gentoo.org>
  jabberd-2.0.11-r1.ebuild:
  Add memdebug USE flag, see bug #152065.