This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] redebug - error reporting.


On Friday 25 October 2013 12:57:19 OndÅej BÃlka wrote:
> On Fri, Oct 25, 2013 at 03:28:55PM +0000, Joseph S. Myers wrote:
> > On Fri, 25 Oct 2013, Ondrej Bilka wrote:
> > > Comments?
> > 
> > It's difficult to tell what the connection to glibc in this message is
> > supposed to be.  If it's that it should be possible to stop in a debugger
> 
> This is followup to preload/undefined behavior detection infrastructure.
> Information what caused undefined behaviour is very useful and this is
> way how to present it. You can show double free, for strcpy overrun show
> allocation that was too small and so.

sure, but i don't think we need anything in glibc other than probe points as 
Joseph said.  whatever tool hooks up to the probe points would take care of 
the UI (messaging/checking/etc...).
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]