Yeuch. Any suggestion on my part would be pure guess work - that looks
like it's almost certainly buried down in wx where only Andreas dares to
venture :-(

Andreas; any ideas?

Regards, Dave

> -----Original Message-----
> From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] 
> Sent: 27 June 2005 16:14
> To: Adam H. Pendleton
> Cc: Dave Page; pgadmin-hackers@postgresql.org; OpenMacNews; 
> [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] [pgadmin-support] mac osX edit 
> table data
> 
> Here's what I've got:
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0xbf7fffc0
> 0x93120364 in BSearch ()
> (gdb) bt
> #0  0x93120364 in BSearch ()
> #1  0x931207e4 in TEventTypeIndex::ContainsType ()
> #2  0x93121dac in GenerateHandlerStackForEventTypeFromTarget ()
> #3  0x931218f0 in DispatchEventToHandlers ()
> #4  0x9312120c in SendEventToEventTargetInternal ()
> #5  0x93121088 in SendEventToEventTargetWithOptions ()
> #6  0x9316602c in SendControlDefGetFocusPart ()
> #7  0x93161d20 in HIView::SetFocusPart ()
> #8  0x93161ae8 in SetKeyboardFocus ()
> #9  0x00313500 in ?? ()
> #10 0x00262890 in ?? ()
> #11 0x002fb810 in ?? ()
> #12 0x00301760 in ?? ()
> #13 0x006a89e8 in wxGrid::DisableCellEditControl ()
> #14 0x00302048 in ?? ()
> #15 0x001b6d38 in ?? ()
> #16 0x001bd670 in ?? ()
> #17 0x001bdcd0 in ?? ()
> #18 0x001bf4d0 in ?? ()
> #19 0x0026be74 in ?? ()
> #20 0x0026c6b8 in ?? ()
> #21 0x93121ab4 in DispatchEventToHandlers ()
> #22 0x9312120c in SendEventToEventTargetInternal ()
> #23 0x93121088 in SendEventToEventTargetWithOptions ()
> #24 0x931621b0 in SendControlDefSetFocusPart ()
> #25 0x93161edc in HIView::SetFocusPartInternal ()
> #26 0x93161d44 in HIView::SetFocusPart ()
> #27 0x93161ae8 in SetKeyboardFocus ()
> ...
> 
> #10680 0x93121ab4 in DispatchEventToHandlers ()
> #10681 0x9312120c in SendEventToEventTargetInternal ()
> #10682 0x93121088 in SendEventToEventTargetWithOptions ()
> #10683 0x931621b0 in SendControlDefSetFocusPart ()
> #10684 0x93161edc in HIView::SetFocusPartInternal ()
> #10685 0x93161d44 in HIView::SetFocusPart ()
> #10686 0x93161ae8 in SetKeyboardFocus ()
> #10687 0x00313500 in ?? ()
> #10688 0x00262890 in ?? ()
> #10689 0x002fb810 in ?? ()
> #10690 0x00301760 in ?? ()
> #10691 0x006a89e8 in wxGrid::DisableCellEditControl ()
> 
> That backtrace goes on forever until I hit Ctrl+C.  Never seen  
> anything like it.  Any ideas?
> 
> On Jun 27, 2005, at 5:59 AM, Adam H. Pendleton wrote:
> 
> > I'll take a look at it today and see what I can come up with.
> >
> > On Jun 27, 2005, at 3:17 AM, Dave Page wrote:
> >
> >
> >> Hi Richard/Florian/Adam,
> >>
> >> I don't know if any of you are on the support list, hence this  
> >> forward.
> >> Could one of you find a few minutes to look at this please?
> >>
> >> Thanks, Dave.
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: [EMAIL PROTECTED]
> >>> [mailto:[EMAIL PROTECTED] On Behalf Of
> >>> John Iannicello
> >>> Sent: 26 June 2005 17:31
> >>> To: pgadmin-support@postgresql.org
> >>> Subject: [pgadmin-support] mac osX edit table data
> >>>
> >>> When I try to add a new data to the table in the  
> 'Table/View Data'
> >>> window,  the program crashes after putting data in one column and
> >>> trying to go to the next column to put data.  I'm using OsX
> >>> 10.3.9 and
> >>> pgadmin version 1.2.2.  If this bug could fixed the rest of the  
> >>> app's
> >>> interface looks great.
> >>>
> >>> John
> >>>
> >>>
> >>> ---------------------------(end of
> >>> broadcast)---------------------------
> >>> TIP 5: Have you checked our extensive FAQ?
> >>>
> >>>                http://www.postgresql.org/docs/faq
> >>>
> >>>
> >>
> >>
> >
> >
> > ---------------------------(end of  
> > broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
> >
> 
> 

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to