[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 272938] please provide a gdb wrapper when std{in,out} are
From:       Pierre Habouzit <madcoder () debian ! org>
Date:       2011-05-10 13:30:55
Message-ID: 20110510133055.2410187A91 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=272938





--- Comment #3 from Pierre Habouzit <madcoder debian org>  2011-05-10 15:30:54 ---
On Tue, May 10, 2011 at 03:08:54PM +0200, Pierre Habouzit wrote:
> On Tue, May 10, 2011 at 02:57:15PM +0200, Christian Borntraeger wrote:
> > https://bugs.kde.org/show_bug.cgi?id=272938
> > 
> > 
> > 
> > 
> > 
> > --- Comment #1 from Christian Borntraeger <borntraeger de ibm com>  2011-05-10 14:57:14 ---
> > > ==30353== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- ==30353== 
> > > ==30353== HEAP SUMMARY:
> > > ==30353==     in use at exit: 0 bytes in 0 blocks
> > > ==30353==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
> > > ==30353== 
> > > ==30353== All heap blocks were freed -- no leaks are possible
> > > ==30353== 
> > > ==30353== For counts of detected and suppressed errors, rerun with: -v
> > > ==30353== Use --track-origins=yes to see where uninitialised values come from
> > > ==30353== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
> > > 
> > > The debugger isn't actually started because stdin is "empty" already (and if it
> > > wasn't it would be re-read by gdb which is even worse).
> > > 
> > > valgrind should wrap calling the debugger recreating sensible std{in,out,err}
> > > using /dev/tty.
> > > 
> > > FWIW this is Debian bug #351823
> > > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351823)
> > > 
> > 
> > This might be the same as 
> > https://bugs.kde.org/show_bug.cgi?id=263423
> > I have a patch in this bugzilla (dont know if it still applies), can you check?
> 
> It's likely to be the same underlying issue indeed, and the patch still
> applies (with fuzz)
> 
> I'll try to see if that fixes the issue for me.

Okay it appears it's not the same issue as your patch doesn't change
anything.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]