git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: SEGV when lookup_* returns NULL

From
MWMorten Welinder <mwelinder@gmail.com>
Date
Nov 28, 2006, 02:23 UTC
Message-ID
<118833cc0611271823t3b1783cem38f031ac26ac0f94@mail.gmail.com>
In-Reply-To
<7v3b84e8cg.fsf@assigned-by-dhcp.cox.net>
> Why?  You would certainly install your own die() handler by that
> time I presume?

Likely, but short of exiting or using longjmp/setjmp what can you do in such a "die"? Not much. And most GUI users will be unhappy with the exit approach.

If there is any chance that the error is not the programmer's fault, a nice library ought to pass the error back somehow.

Previous: Junio C Hamano
Message 5 of 5 in “SEGV when lookup_* returns NULL”
  1. Martin WaitzNov 27, 2006
  2. Junio C HamanoNov 27, 2006
  3. Johannes SchindelinNov 27, 2006
  4. Junio C HamanoNov 28, 2006
  5. Morten WelinderNov 28, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.